From: Ryan Roberts <ryan.roberts@arm.com>
To: Barry Song <21cnbao@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
david@redhat.com
Cc: linux-mm@kvack.org, cerasuolodomenico@gmail.com,
chrisl@kernel.org, kasong@tencent.com, peterx@redhat.com,
surenb@google.com, v-songbaohua@oppo.com, willy@infradead.org,
yosryahmed@google.com, yuzhao@google.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] mm: add per-order mTHP alloc and swpout counters
Date: Thu, 11 Apr 2024 17:45:41 +0100 [thread overview]
Message-ID: <e23420bb-0d97-4546-a2ae-8bfe3c10e259@arm.com> (raw)
In-Reply-To: <CAGsJ_4zpKmha2YtnsuDdda9_w4MtPZrk=SbdnBhJbdoA9HbogA@mail.gmail.com>
On 05/04/2024 23:04, Barry Song wrote:
> On Sat, Apr 6, 2024 at 9:11 AM Andrew Morton <akpm@linux-foundation.org> wrote:
>>
>> On Fri, 5 Apr 2024 23:27:02 +1300 Barry Song <21cnbao@gmail.com> wrote:
>>
>>> The patchset introduces a framework to facilitate mTHP counters, starting
>>> with the allocation and swap-out counters. Currently, only four new nodes
>>> are appended to the stats directory for each mTHP size.
>>>
>>> /sys/kernel/mm/transparent_hugepage/hugepages-<size>/stats
>>> anon_alloc
>>> anon_alloc_fallback
>>> anon_swpout
>>> anon_swpout_fallback
>>
>> Please let's get these documented?
>
> Sure, I will do it.
>
> Furthermore, after careful consideration, I suggest renaming anon_alloc to
> anon_fault_alloc and anon_alloc_fallback to anon_fault_fallback. This
> renaming is consistent with the naming convention observed in
> thp_fault_alloc and thp_fault_fallback in vmstat. Additionally, this
> modification will facilitate the handling of large folio swap-ins.
>
> /sys/kernel/mm/transparent_hugepage/hugepages-<size>/stats
> anon_fault_alloc,
> anon_fault_fallback,
> anon_swpin_alloc,
> anon_swpin_fallback,
>
> Otherwise, without this renaming, it would be difficult to
> differentiate fault_alloc
> from swpin_alloc.
>
> Hi David, Ryan,
> I would also appreciate your input on the modification I am considering.
Yes, this makes sense to me!
>
>> Documentation/admin-guide/mm/transhuge.rst seems to be the place, and
>> under Documentation/ABI.
>
> Thanks
> Barry
prev parent reply other threads:[~2024-04-11 16:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 10:27 Barry Song
2024-04-05 10:27 ` [PATCH v4 1/2] mm: add per-order mTHP anon_alloc and anon_alloc_fallback counters Barry Song
2024-04-11 16:38 ` Ryan Roberts
2024-04-11 22:40 ` Barry Song
2024-04-12 9:16 ` Ryan Roberts
2024-04-12 9:27 ` Barry Song
2024-04-05 10:27 ` [PATCH v4 2/2] mm: add per-order mTHP anon_swpout and anon_swpout_fallback counters Barry Song
2024-04-11 16:43 ` Ryan Roberts
2024-04-11 21:52 ` Barry Song
2024-04-05 20:11 ` [PATCH v4 0/2] mm: add per-order mTHP alloc and swpout counters Andrew Morton
2024-04-05 22:04 ` Barry Song
2024-04-11 16:45 ` Ryan Roberts [this message]
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=e23420bb-0d97-4546-a2ae-8bfe3c10e259@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-kernel@vger.kernel.org \
--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