From: David Hildenbrand <david@redhat.com>
To: Baolin Wang <baolin.wang@linux.alibaba.com>,
Bang Li <libang.li@antgroup.com>,
hughd@google.com, akpm@linux-foundation.org
Cc: ryan.roberts@arm.com, wangkefeng.wang@huawei.com, ziy@nvidia.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Barry Song <21cnbao@gmail.com>
Subject: Re: [PATCH] support "THPeligible" semantics for mTHP with anonymous shmem
Date: Mon, 1 Jul 2024 08:55:20 +0200 [thread overview]
Message-ID: <2972d75a-ab26-4da7-88fa-81bed955cf52@redhat.com> (raw)
In-Reply-To: <b2e6fac2-7c23-4a92-8d89-ff29b8566967@linux.alibaba.com>
On 01.07.24 08:47, Baolin Wang wrote:
> CC Barry.
>
> On 2024/6/28 18:49, Bang Li wrote:
>> After the commit 7fb1b252afb5 ("mm: shmem: add mTHP support for
>> anonymous shmem"), we can configure different policies through
>> the multi-size THP sysfs interface for anonymous shmem. But
>> currently "THPeligible" indicates only whether the mapping is
>> eligible for allocating THP-pages as well as the THP is PMD
>> mappable or not for anonymous shmem, we need to support semantics
>> for mTHP with anonymous shmem similar to those for mTHP with
>> anonymous memory.
>
> I did not see a consensus that "THP*" related statistics should contain
> mTHP in previous discussion [1].
>
> In addition, if we all agree that "THPeligible" should include mTHP
> statistics, you should update the corresponding documentation to keep
> consistency.
>
> [1]
> https://lore.kernel.org/linux-mm/202406262300.iAURISyJ-lkp@intel.com/T/#md7a77056110cebcc2a9b3cd7e4a8d682667f6ba5
>
Fortunately, documentation (Documentation/filesystems/proc.rst) says:
"THPeligible" indicates whether the mapping is eligible for allocating
naturally aligned THP pages of any currently enabled size. 1 if true, 0
otherwise."
So that documentation is already pretty clear (we just have to make sure
the other ones are properly documented, for example as raised in reply
to [1]).
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-07-01 6:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 10:49 Bang Li
2024-07-01 6:47 ` Baolin Wang
2024-07-01 6:55 ` David Hildenbrand [this message]
2024-07-01 7:18 ` Baolin Wang
2024-07-01 8:22 ` Bang Li
2024-07-01 6:57 ` David Hildenbrand
2024-07-01 8:24 ` Bang Li
2024-07-01 7:55 ` Ryan Roberts
2024-07-01 8:33 ` Baolin Wang
2024-07-01 8:40 ` Ryan Roberts
2024-07-01 8:46 ` Baolin Wang
2024-07-01 8:48 ` David Hildenbrand
2024-07-01 8:50 ` Ryan Roberts
2024-07-01 8:57 ` David Hildenbrand
2024-07-01 9:14 ` Ryan Roberts
2024-07-01 9:17 ` David Hildenbrand
2024-07-01 10:16 ` Ryan Roberts
2024-07-01 10:22 ` David Hildenbrand
2024-07-01 18:20 ` Yang Shi
2024-07-02 8:24 ` Ryan Roberts
2024-07-02 8:28 ` David Hildenbrand
2024-07-03 16:08 ` Yang Shi
2024-07-03 16:19 ` David Hildenbrand
2024-07-04 9:43 ` Ryan Roberts
2024-07-09 19:01 ` Yang Shi
2024-07-01 9:43 ` Bang Li
2024-07-01 11:12 ` Baolin Wang
2024-07-01 14:51 ` Bang Li
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=2972d75a-ab26-4da7-88fa-81bed955cf52@redhat.com \
--to=david@redhat.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=hughd@google.com \
--cc=libang.li@antgroup.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryan.roberts@arm.com \
--cc=wangkefeng.wang@huawei.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