From: Ryan Roberts <ryan.roberts@arm.com>
To: Barry Song <21cnbao@gmail.com>, David Hildenbrand <david@redhat.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
willy@infradead.org, cerasuolodomenico@gmail.com,
kasong@tencent.com, surenb@google.com, v-songbaohua@oppo.com,
yosryahmed@google.com, yuzhao@google.com, chrisl@kernel.org,
peterx@redhat.com
Subject: Re: [PATCH v2] mm: add per-order mTHP alloc_success and alloc_fail counters
Date: Wed, 3 Apr 2024 09:18:06 +0100 [thread overview]
Message-ID: <c1d7d4e2-d062-49fb-ba24-69846423f090@arm.com> (raw)
In-Reply-To: <CAGsJ_4yyW+HpACCR_HtS4kJzHZRmYqrRaG2nnFktEdVgkutV5A@mail.gmail.com>
On 02/04/2024 22:29, Barry Song wrote:
> On Wed, Apr 3, 2024 at 7:46 AM David Hildenbrand <david@redhat.com> wrote:
>>
>> On 28.03.24 10:51, Barry Song wrote:
>>> From: Barry Song <v-songbaohua@oppo.com>
>>>
>>> Profiling a system blindly with mTHP has become challenging due
>>> to the lack of visibility into its operations. Presenting the
>>> success rate of mTHP allocations appears to be pressing need.
>>>
>>> Recently, I've been experiencing significant difficulty debugging
>>> performance improvements and regressions without these figures.
>>> It's crucial for us to understand the true effectiveness of
>>> mTHP in real-world scenarios, especially in systems with
>>> fragmented memory.
>>>
>>> This patch sets up the framework for per-order mTHP counters,
>>> starting with the introduction of alloc_success and alloc_fail
>>> counters. Incorporating additional counters should now be
>>> straightforward as well.
>>>
>>> The initial two unsigned longs for each event are unused, given
>>> that order-0 and order-1 are not mTHP. Nonetheless, this refinement
>>> improves code clarity.
>>>
>>> Signed-off-by: Barry Song <v-songbaohua@oppo.com>
>>> ---
>>> -v2:
>>> * move to sysfs and provide per-order counters; David, Ryan, Willy
>>> -v1:
>>> https://lore.kernel.org/linux-mm/20240326030103.50678-1-21cnbao@gmail.com/
>>>
>>> include/linux/huge_mm.h | 17 +++++++++++++
>>> mm/huge_memory.c | 54 +++++++++++++++++++++++++++++++++++++++++
>>> mm/memory.c | 3 +++
>>> 3 files changed, 74 insertions(+)
>>>
>>> diff --git a/include/linux/huge_mm.h b/include/linux/huge_mm.h
>>> index e896ca4760f6..27fa26a22a8f 100644
>>> --- a/include/linux/huge_mm.h
>>> +++ b/include/linux/huge_mm.h
>>> @@ -264,6 +264,23 @@ unsigned long thp_vma_allowable_orders(struct vm_area_struct *vma,
>>> enforce_sysfs, orders);
>>> }
>>>
>>> +enum thp_event_item {
>>> + THP_ALLOC_SUCCESS,
>>> + THP_ALLOC_FAIL,
>>> + NR_THP_EVENT_ITEMS
>>> +};
>>
>> I'm wondering if these should be ANON specific for now. We might want to
>> add others (shmem, file) in the future.
>
> I've two ways to do that
> 1. rename to ANON_THP_ALLOC, so that I can have SHMEM_THP_ALLOC, FILE_THP_ALLOC
> in the future;
> 2. let THP_ALLOC cover all of shmem, file and anon.
>
> following vmstat, actually 1 might be better as we have both THP_FAULT_ALLOC and
> THP_FILE_ALLOC for pmd-mapped THP.
>
> #ifdef CONFIG_TRANSPARENT_HUGEPAGE
> THP_FAULT_ALLOC,
> THP_FAULT_FALLBACK,
> THP_FAULT_FALLBACK_CHARGE,
> THP_COLLAPSE_ALLOC,
> THP_COLLAPSE_ALLOC_FAILED,
> THP_FILE_ALLOC,
> THP_FILE_FALLBACK,
> THP_FILE_FALLBACK_CHARGE,
> THP_FILE_MAPPED,
> THP_SPLIT_PAGE,
> THP_SPLIT_PAGE_FAILED,
> THP_DEFERRED_SPLIT_PAGE,
> THP_SPLIT_PMD,
> THP_SCAN_EXCEED_NONE_PTE,
> THP_SCAN_EXCEED_SWAP_PTE,
> THP_SCAN_EXCEED_SHARED_PTE,
> #ifdef CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE_PUD
> THP_SPLIT_PUD,
> #endif
> THP_ZERO_PAGE_ALLOC,
> THP_ZERO_PAGE_ALLOC_FAILED,
> THP_SWPOUT,
> THP_SWPOUT_FALLBACK,
> #endif
>
> And reading mm/shmem.c, obviously, shmem is using THP_FILE_ALLOC.
>
> I will rename it to ANON_THP_ALLOC in v3, let me know if you disagree :-)
I don't think the name of the enum is important - its an implementation detail
that can be changed. Its the name of the sysfs file that matters. Although of
course its nice to keep them in sync from a maintenance pov.
Currently they are called "alloc_success" and "alloc_fail" I believe? Perhaps
"anon_alloc" and "anon_alloc_fallback" are a bit more in keeping with vmstat?
I'm assuming that:
vmstat:thp_fault_alloc == hugepages-2048kB/stats/anon_alloc
vmstat:thp_fault_alloc_fallback == hugepages-2048kB/stats/anon_alloc_fallback
?
Thanks,
Ryan
>
>>
>> --
>> Cheers,
>>
>> David / dhildenb
>>
>
> Thanks
> Barry
next prev parent reply other threads:[~2024-04-03 8:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 9:51 Barry Song
2024-04-01 14:46 ` Yu Zhao
2024-04-01 20:40 ` Barry Song
2024-04-02 8:58 ` Ryan Roberts
2024-04-02 9:40 ` Barry Song
2024-04-02 10:44 ` Ryan Roberts
2024-04-02 22:14 ` Barry Song
2024-04-03 8:03 ` Ryan Roberts
2024-04-02 18:46 ` David Hildenbrand
2024-04-02 21:29 ` Barry Song
2024-04-03 8:13 ` David Hildenbrand
2024-04-03 20:47 ` Barry Song
2024-04-03 8:18 ` Ryan Roberts [this message]
2024-04-03 8:24 ` David Hildenbrand
2024-04-03 8:46 ` Ryan Roberts
2024-04-03 9:05 ` David Hildenbrand
2024-04-03 21:06 ` Barry Song
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=c1d7d4e2-d062-49fb-ba24-69846423f090@arm.com \
--to=ryan.roberts@arm.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cerasuolodomenico@gmail.com \
--cc=chrisl@kernel.org \
--cc=david@redhat.com \
--cc=kasong@tencent.com \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.com \
--cc=surenb@google.com \
--cc=v-songbaohua@oppo.com \
--cc=willy@infradead.org \
--cc=yosryahmed@google.com \
--cc=yuzhao@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