From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Nico Pache <npache@redhat.com>
Cc: linux-mm@kvack.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
akpm@linux-foundation.org, corbet@lwn.net, rostedt@goodmis.org,
mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
david@redhat.com, baohua@kernel.org, ryan.roberts@arm.com,
willy@infradead.org, peterx@redhat.com, ziy@nvidia.com,
wangkefeng.wang@huawei.com, usamaarif642@gmail.com,
sunnanyong@huawei.com, vishal.moola@gmail.com,
thomas.hellstrom@linux.intel.com, yang@os.amperecomputing.com,
kirill.shutemov@linux.intel.com, aarcange@redhat.com,
raquini@redhat.com, dev.jain@arm.com, anshuman.khandual@arm.com,
catalin.marinas@arm.com, tiwai@suse.de, will@kernel.org,
dave.hansen@linux.intel.com, jack@suse.cz, cl@gentwo.org,
jglisse@google.com, surenb@google.com, zokeefe@google.com,
hannes@cmpxchg.org, rientjes@google.com, mhocko@suse.com,
rdunlap@infradead.org, lorenzo.stoakes@oracle.com,
Liam.Howlett@oracle.com
Subject: Re: [PATCH v5 06/12] khugepaged: introduce khugepaged_scan_bitmap for mTHP support
Date: Fri, 2 May 2025 09:23:42 +0800 [thread overview]
Message-ID: <83a66442-b7c7-42e7-af4e-fd211d8ed6f8@linux.alibaba.com> (raw)
In-Reply-To: <CAA1CXcDarV2LqLcSRpb=a_A5YFBc26dBT0cCYdLj-8jGKZ53Yw@mail.gmail.com>
On 2025/5/2 07:03, Nico Pache wrote:
> On Wed, Apr 30, 2025 at 12:56 PM Nico Pache <npache@redhat.com> wrote:
>>
>> On Wed, Apr 30, 2025 at 4:08 AM Baolin Wang
>> <baolin.wang@linux.alibaba.com> wrote:
>>>
>>>
>>>
>>> On 2025/4/29 02:12, Nico Pache wrote:
>>>> khugepaged scans anons PMD ranges for potential collapse to a hugepage.
>>>> To add mTHP support we use this scan to instead record chunks of utilized
>>>> sections of the PMD.
>>>>
>>>> khugepaged_scan_bitmap uses a stack struct to recursively scan a bitmap
>>>> that represents chunks of utilized regions. We can then determine what
>>>> mTHP size fits best and in the following patch, we set this bitmap while
>>>> scanning the anon PMD.
>>>>
>>>> max_ptes_none is used as a scale to determine how "full" an order must
>>>> be before being considered for collapse.
>>>>
>>>> When attempting to collapse an order that has its order set to "always"
>>>> lets always collapse to that order in a greedy manner without
>>>> considering the number of bits set.
>>>>
>>>> Signed-off-by: Nico Pache <npache@redhat.com>
>>>> ---
>>>> include/linux/khugepaged.h | 4 ++
>>>> mm/khugepaged.c | 94 ++++++++++++++++++++++++++++++++++----
>>>> 2 files changed, 89 insertions(+), 9 deletions(-)
>>>>
>>>> diff --git a/include/linux/khugepaged.h b/include/linux/khugepaged.h
>>>> index 1f46046080f5..18fe6eb5051d 100644
>>>> --- a/include/linux/khugepaged.h
>>>> +++ b/include/linux/khugepaged.h
>>>> @@ -1,6 +1,10 @@
>>>> /* SPDX-License-Identifier: GPL-2.0 */
>>>> #ifndef _LINUX_KHUGEPAGED_H
>>>> #define _LINUX_KHUGEPAGED_H
>>>> +#define KHUGEPAGED_MIN_MTHP_ORDER 2
>>>
>>> Still better to add some comments to explain explicitly why choose 2 as
>>> the MIN_MTHP_ORDER.
>> Ok i'll add a note that explicitly states that the min order of anon mTHPs is 2
>>>
>>>> +#define KHUGEPAGED_MIN_MTHP_NR (1<<KHUGEPAGED_MIN_MTHP_ORDER)
>>>> +#define MAX_MTHP_BITMAP_SIZE (1 << (ilog2(MAX_PTRS_PER_PTE) - KHUGEPAGED_MIN_MTHP_ORDER))
>>>> +#define MTHP_BITMAP_SIZE (1 << (HPAGE_PMD_ORDER - KHUGEPAGED_MIN_MTHP_ORDER))
>>>>
>>>> extern unsigned int khugepaged_max_ptes_none __read_mostly;
>>>> #ifdef CONFIG_TRANSPARENT_HUGEPAGE
>>>> diff --git a/mm/khugepaged.c b/mm/khugepaged.c
>>>> index e21998a06253..6e67db86409a 100644
>>>> --- a/mm/khugepaged.c
>>>> +++ b/mm/khugepaged.c
>>>> @@ -94,6 +94,11 @@ static DEFINE_READ_MOSTLY_HASHTABLE(mm_slots_hash, MM_SLOTS_HASH_BITS);
>>>>
>>>> static struct kmem_cache *mm_slot_cache __ro_after_init;
>>>>
>>>> +struct scan_bit_state {
>>>> + u8 order;
>>>> + u16 offset;
>>>> +};
>>>> +
>>>> struct collapse_control {
>>>> bool is_khugepaged;
>>>>
>>>> @@ -102,6 +107,18 @@ struct collapse_control {
>>>>
>>>> /* nodemask for allocation fallback */
>>>> nodemask_t alloc_nmask;
>>>> +
>>>> + /*
>>>> + * bitmap used to collapse mTHP sizes.
>>>> + * 1bit = order KHUGEPAGED_MIN_MTHP_ORDER mTHP
>>>> + */
>>>> + DECLARE_BITMAP(mthp_bitmap, MAX_MTHP_BITMAP_SIZE);
>>>> + DECLARE_BITMAP(mthp_bitmap_temp, MAX_MTHP_BITMAP_SIZE);
>>>> + struct scan_bit_state mthp_bitmap_stack[MAX_MTHP_BITMAP_SIZE];
>>>> +};
>>>> +
>>>> +struct collapse_control khugepaged_collapse_control = {
>>>> + .is_khugepaged = true,
>>>> };
>>>>
>>>> /**
>>>> @@ -851,10 +868,6 @@ static void khugepaged_alloc_sleep(void)
>>>> remove_wait_queue(&khugepaged_wait, &wait);
>>>> }
>>>>
>>>> -struct collapse_control khugepaged_collapse_control = {
>>>> - .is_khugepaged = true,
>>>> -};
>>>> -
>>>> static bool khugepaged_scan_abort(int nid, struct collapse_control *cc)
>>>> {
>>>> int i;
>>>> @@ -1118,7 +1131,8 @@ static int alloc_charge_folio(struct folio **foliop, struct mm_struct *mm,
>>>>
>>>> static int collapse_huge_page(struct mm_struct *mm, unsigned long address,
>>>> int referenced, int unmapped,
>>>> - struct collapse_control *cc)
>>>> + struct collapse_control *cc, bool *mmap_locked,
>>>> + u8 order, u16 offset)
>>>> {
>>>> LIST_HEAD(compound_pagelist);
>>>> pmd_t *pmd, _pmd;
>>>> @@ -1137,8 +1151,12 @@ static int collapse_huge_page(struct mm_struct *mm, unsigned long address,
>>>> * The allocation can take potentially a long time if it involves
>>>> * sync compaction, and we do not need to hold the mmap_lock during
>>>> * that. We will recheck the vma after taking it again in write mode.
>>>> + * If collapsing mTHPs we may have already released the read_lock.
>>>> */
>>>> - mmap_read_unlock(mm);
>>>> + if (*mmap_locked) {
>>>> + mmap_read_unlock(mm);
>>>> + *mmap_locked = false;
>>>> + }
>>>>
>>>> result = alloc_charge_folio(&folio, mm, cc, HPAGE_PMD_ORDER);
>>>> if (result != SCAN_SUCCEED)
>>>> @@ -1273,12 +1291,72 @@ static int collapse_huge_page(struct mm_struct *mm, unsigned long address,
>>>> out_up_write:
>>>> mmap_write_unlock(mm);
>>>> out_nolock:
>>>> + *mmap_locked = false;
>>>> if (folio)
>>>> folio_put(folio);
>>>> trace_mm_collapse_huge_page(mm, result == SCAN_SUCCEED, result);
>>>> return result;
>>>> }
>>>>
>>>> +// Recursive function to consume the bitmap
>>>
>>> Nit: please use '/* Xxxx */' for comments in this patch.
>>>
>>>> +static int khugepaged_scan_bitmap(struct mm_struct *mm, unsigned long address,
>>>> + int referenced, int unmapped, struct collapse_control *cc,
>>>> + bool *mmap_locked, unsigned long enabled_orders)
>>>> +{
>>>> + u8 order, next_order;
>>>> + u16 offset, mid_offset;
>>>> + int num_chunks;
>>>> + int bits_set, threshold_bits;
>>>> + int top = -1;
>>>> + int collapsed = 0;
>>>> + int ret;
>>>> + struct scan_bit_state state;
>>>> + bool is_pmd_only = (enabled_orders == (1 << HPAGE_PMD_ORDER));
>>>> +
>>>> + cc->mthp_bitmap_stack[++top] = (struct scan_bit_state)
>>>> + { HPAGE_PMD_ORDER - KHUGEPAGED_MIN_MTHP_ORDER, 0 };
>>>> +
>>>> + while (top >= 0) {
>>>> + state = cc->mthp_bitmap_stack[top--];
>>>> + order = state.order + KHUGEPAGED_MIN_MTHP_ORDER;
>>>> + offset = state.offset;
>>>> + num_chunks = 1 << (state.order);
>>>> + // Skip mTHP orders that are not enabled
>>>> + if (!test_bit(order, &enabled_orders))
>>>> + goto next;
>>>> +
>>>> + // copy the relavant section to a new bitmap
>>>> + bitmap_shift_right(cc->mthp_bitmap_temp, cc->mthp_bitmap, offset,
>>>> + MTHP_BITMAP_SIZE);
>>>> +
>>>> + bits_set = bitmap_weight(cc->mthp_bitmap_temp, num_chunks);
>>>> + threshold_bits = (HPAGE_PMD_NR - khugepaged_max_ptes_none - 1)
>>>> + >> (HPAGE_PMD_ORDER - state.order);
>>>> +
>>>> + //Check if the region is "almost full" based on the threshold
>>>> + if (bits_set > threshold_bits || is_pmd_only
>>>> + || test_bit(order, &huge_anon_orders_always)) {
>>>
>>> When testing this patch, I disabled the PMD-sized THP and enabled
>>> 64K-sized mTHP, but it still attempts to collapse into a PMD-sized THP
>>> (since bits_set > threshold_bits is ture). This doesn't seem reasonable?
>> We are still required to have PMD enabled for mTHP collapse to work.
>> It's a limitation of the current khugepaged code (it currently only
>> adds mm_slots when PMD is enabled).
>> We've discussed this in the past and are looking for a proper way
>> forward, but the solution becomes tricky.
>>
>> However I'm surprised that it still collapses due to the code below.
>> I'll test this out later today.
>
> Following up, you are correct, if I disable the PMD size within the
> mTHP enabled settings (echo never >
> /sys/kernel/mm/transparent_hugepage/hugepages-2048kB/enabled) it still
> collapses to PMDs. I believe the global variable takes precedent. I'm
> not sure what the correct behavior is... I will look into it further
>
>> + if (!test_bit(order, &enabled_orders))
>> + goto next;
IMO, we should respect the mTHP sysfs control interfaces and use the
'TVA_ENFORCE_SYSFS' flag when determining allowable orders through
thp_vma_allowable_orders().
next prev parent reply other threads:[~2025-05-02 1:23 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 18:12 [PATCH v5 00/12] khugepaged: " Nico Pache
2025-04-28 18:12 ` [PATCH v5 01/12] khugepaged: rename hpage_collapse_* to khugepaged_* Nico Pache
2025-04-29 13:41 ` Zi Yan
2025-04-30 7:47 ` Baolin Wang
2025-04-28 18:12 ` [PATCH v5 02/12] introduce khugepaged_collapse_single_pmd to unify khugepaged and madvise_collapse Nico Pache
2025-04-30 7:56 ` Baolin Wang
2025-04-28 18:12 ` [PATCH v5 03/12] khugepaged: generalize hugepage_vma_revalidate for mTHP support Nico Pache
2025-04-28 18:12 ` [PATCH v5 04/12] khugepaged: generalize alloc_charge_folio() Nico Pache
2025-04-28 18:12 ` [PATCH v5 05/12] khugepaged: generalize __collapse_huge_page_* for mTHP support Nico Pache
2025-04-28 18:12 ` [PATCH v5 06/12] khugepaged: introduce khugepaged_scan_bitmap " Nico Pache
2025-04-30 10:08 ` Baolin Wang
2025-04-30 18:56 ` Nico Pache
2025-05-01 23:03 ` Nico Pache
2025-05-02 1:23 ` Baolin Wang [this message]
2025-06-06 16:37 ` Dev Jain
2025-06-07 12:48 ` Nico Pache
2025-04-28 18:12 ` [PATCH v5 07/12] khugepaged: add " Nico Pache
2025-04-30 20:51 ` Jann Horn
2025-05-01 22:29 ` Nico Pache
2025-05-02 6:29 ` David Hildenbrand
2025-05-02 12:50 ` Jann Horn
2025-05-02 15:18 ` David Hildenbrand
2025-05-02 15:24 ` Lorenzo Stoakes
2025-05-02 15:39 ` David Hildenbrand
2025-05-02 15:26 ` Jann Horn
2025-05-02 15:30 ` Nico Pache
2025-05-02 15:42 ` David Hildenbrand
2025-05-01 12:58 ` Hugh Dickins
2025-05-01 16:15 ` Andrew Morton
2025-05-01 22:30 ` Nico Pache
2025-04-28 18:12 ` [PATCH v5 08/12] khugepaged: skip collapsing mTHP to smaller orders Nico Pache
2025-04-30 10:09 ` Baolin Wang
2025-04-28 18:12 ` [PATCH v5 09/12] khugepaged: avoid unnecessary mTHP collapse attempts Nico Pache
2025-04-30 10:12 ` Baolin Wang
2025-04-30 18:43 ` Nico Pache
2025-04-28 18:12 ` [PATCH v5 10/12] khugepaged: improve tracepoints for mTHP orders Nico Pache
2025-04-28 18:12 ` [PATCH v5 11/12] khugepaged: add per-order mTHP khugepaged stats Nico Pache
2025-04-28 18:12 ` [PATCH v5 12/12] Documentation: mm: update the admin guide for mTHP collapse Nico Pache
2025-04-29 5:10 ` Bagas Sanjaya
2025-04-29 16:38 ` Christoph Lameter (Ampere)
2025-04-29 17:15 ` David Hildenbrand
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=83a66442-b7c7-42e7-af4e-fd211d8ed6f8@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=Liam.Howlett@oracle.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=baohua@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cl@gentwo.org \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=hannes@cmpxchg.org \
--cc=jack@suse.cz \
--cc=jglisse@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mhocko@suse.com \
--cc=npache@redhat.com \
--cc=peterx@redhat.com \
--cc=raquini@redhat.com \
--cc=rdunlap@infradead.org \
--cc=rientjes@google.com \
--cc=rostedt@goodmis.org \
--cc=ryan.roberts@arm.com \
--cc=sunnanyong@huawei.com \
--cc=surenb@google.com \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tiwai@suse.de \
--cc=usamaarif642@gmail.com \
--cc=vishal.moola@gmail.com \
--cc=wangkefeng.wang@huawei.com \
--cc=will@kernel.org \
--cc=willy@infradead.org \
--cc=yang@os.amperecomputing.com \
--cc=ziy@nvidia.com \
--cc=zokeefe@google.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
all inboxes | Powered by JetHome®