From: David Hildenbrand <david@redhat.com>
To: Barry Song <21cnbao@gmail.com>,
akpm@linux-foundation.org, linux-mm@kvack.org
Cc: baolin.wang@linux.alibaba.com, chrisl@kernel.org,
hanchuanhua@oppo.com, ioworker0@gmail.com,
kaleshsingh@google.com, kasong@tencent.com,
linux-kernel@vger.kernel.org, ryan.roberts@arm.com,
v-songbaohua@oppo.com, yuanshuai@oppo.com, ziy@nvidia.com,
usamaarif642@gmail.com
Subject: Re: [PATCH v3 1/2] mm: collect the number of anon large folios
Date: Fri, 23 Aug 2024 13:39:00 +0200 [thread overview]
Message-ID: <a4fdb1a7-3748-4aa5-bd44-7d56454c3f79@redhat.com> (raw)
In-Reply-To: <7f9e6bf8-ec58-4525-ace6-98ba58de3172@redhat.com>
On 23.08.24 13:31, David Hildenbrand wrote:
> On 23.08.24 00:40, Barry Song wrote:
>> From: Barry Song <v-songbaohua@oppo.com>
>>
>
> Nit: "anon large folios" come in two flavors: THP and hugetlb.
>
> I suggest to just call it "anon THP" in the context of both patches
> subjects/descriptions (sorry, I should have realized that earlier) to
> make it clearer.
>
> This patch I would call
>
> "mm: count the number of anonymous THPs per size"
Oh, and in the cover letter subject you did it right. Just be consistent
:) (I don't care if we call it THP or mTHP here, whatever floats your boat)
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-08-23 11:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 22:40 [PATCH v3 0/2] mm: collect the number of anon mTHP Barry Song
2024-08-22 22:40 ` [PATCH v3 1/2] mm: collect the number of anon large folios Barry Song
2024-08-23 11:31 ` David Hildenbrand
2024-08-23 11:39 ` David Hildenbrand [this message]
2024-08-22 22:40 ` [PATCH v3 2/2] mm: collect the number of anon large folios partially mapped Barry Song
2024-08-23 11:37 ` 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=a4fdb1a7-3748-4aa5-bd44-7d56454c3f79@redhat.com \
--to=david@redhat.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=chrisl@kernel.org \
--cc=hanchuanhua@oppo.com \
--cc=ioworker0@gmail.com \
--cc=kaleshsingh@google.com \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryan.roberts@arm.com \
--cc=usamaarif642@gmail.com \
--cc=v-songbaohua@oppo.com \
--cc=yuanshuai@oppo.com \
--cc=ziy@nvidia.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;
as well as URLs for NNTP newsgroup(s).