From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: "Vishal Moola (Oracle)" <vishal.moola@gmail.com>, <linux-mm@kvack.org>
Cc: <linux-kernel@vger.kernel.org>, <akpm@linux-foundation.org>,
<shy828301@gmail.com>
Subject: Re: [PATCH 4/5] mm/khugepaged: Convert alloc_charge_hpage() to use folios
Date: Tue, 17 Oct 2023 11:48:26 +0800 [thread overview]
Message-ID: <84cdc2c3-e5e3-469b-b265-8df3e72a8c2f@huawei.com> (raw)
In-Reply-To: <20231016200510.7387-5-vishal.moola@gmail.com>
On 2023/10/17 4:05, Vishal Moola (Oracle) wrote:
> Also convert hpage_collapse_alloc_page() to
> hpage_collapse_alloc_folio().
>
> This removes 1 call to compound_head() and helps convert khugepaged to
> use folios throughout.
>
> Signed-off-by: Vishal Moola (Oracle) <vishal.moola@gmail.com>
> ---
> mm/khugepaged.c | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/mm/khugepaged.c b/mm/khugepaged.c
> index fa21a53ce0c0..70bba8ddea13 100644
> --- a/mm/khugepaged.c
> +++ b/mm/khugepaged.c
> @@ -886,16 +886,16 @@ static int hpage_collapse_find_target_node(struct collapse_control *cc)
> }
> #endif
>
> -static bool hpage_collapse_alloc_page(struct page **hpage, gfp_t gfp, int node,
> +static bool hpage_collapse_alloc_folio(struct folio **folio, gfp_t gfp, int node,
> nodemask_t *nmask)
> {
> - *hpage = __alloc_pages(gfp, HPAGE_PMD_ORDER, node, nmask);
> - if (unlikely(!*hpage)) {
> + *folio = __folio_alloc(gfp, HPAGE_PMD_ORDER, node, nmask);
> +
> + if (unlikely(!*folio)) {
> count_vm_event(THP_COLLAPSE_ALLOC_FAILED);
> return false;
> }
>
> - folio_prep_large_rmappable((struct folio *)*hpage);
> count_vm_event(THP_COLLAPSE_ALLOC);
> return true;
> }
> @@ -1062,15 +1062,16 @@ static int alloc_charge_hpage(struct page **hpage, struct mm_struct *mm,
> int node = hpage_collapse_find_target_node(cc);
> struct folio *folio;
>
> - if (!hpage_collapse_alloc_page(hpage, gfp, node, &cc->alloc_nmask))
> + if (!hpage_collapse_alloc_folio(&folio, gfp, node, &cc->alloc_nmask))
> return SCAN_ALLOC_HUGE_PAGE_FAIL;
>
> - folio = page_folio(*hpage);
> if (unlikely(mem_cgroup_charge(folio, mm, gfp))) {
> folio_put(folio);
> *hpage = NULL;
> return SCAN_CGROUP_CHARGE_FAIL;
> }
> +
> + *hpage = folio_page(folio, 0);
> count_memcg_page_event(*hpage, THP_COLLAPSE_ALLOC);
count_memcg_folio_events()and kill count_memcg_page_event?
>
> return SCAN_SUCCEED;
next prev parent reply other threads:[~2023-10-17 3:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 20:05 [PATCH 0/5] Some khugepaged folio conversions Vishal Moola (Oracle)
2023-10-16 20:05 ` [PATCH 1/5] mm/khugepaged: Convert __collapse_huge_page_isolate() to use folios Vishal Moola (Oracle)
2023-10-16 20:05 ` [PATCH 2/5] mm/khugepaged: Convert hpage_collapse_scan_pmd() " Vishal Moola (Oracle)
2023-10-17 20:41 ` Yang Shi
2023-10-18 17:33 ` Vishal Moola
2023-10-16 20:05 ` [PATCH 3/5] mm/khugepaged: Convert is_refcount_suitable() " Vishal Moola (Oracle)
2023-10-16 20:05 ` [PATCH 4/5] mm/khugepaged: Convert alloc_charge_hpage() " Vishal Moola (Oracle)
2023-10-17 3:48 ` Kefeng Wang [this message]
2023-10-18 17:21 ` Vishal Moola
2023-10-16 20:05 ` [PATCH 5/5] mm/khugepaged: Convert collapse_pte_mapped_thp() " Vishal Moola (Oracle)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84cdc2c3-e5e3-469b-b265-8df3e72a8c2f@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shy828301@gmail.com \
--cc=vishal.moola@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox