From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: David Hildenbrand <david@redhat.com>, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: mm: fix the incorrect 'FileHugeMapped' field
Date: Wed, 18 Dec 2024 14:28:25 +0800 [thread overview]
Message-ID: <2328c2df-fb6c-4c7f-8247-5061b0f94f06@linux.alibaba.com> (raw)
In-Reply-To: <dd96e6d4-b8fe-4360-b6eb-f6375df9eaf2@redhat.com>
On 2024/12/17 19:59, David Hildenbrand wrote:
> On 17.12.24 09:55, Baolin Wang wrote:
>> The '/proc/PID/smaps' does not have the 'FileHugeMapped' field to
>> count the
>> file transparent huge pages, instead, the 'FilePmdMapped' field should be
>> used. Fix it.
>>
>> Signed-off-by: Baolin Wang <baolin.wang@linux.alibaba.com>
>> ---
>> Documentation/admin-guide/mm/transhuge.rst | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/Documentation/admin-guide/mm/transhuge.rst
>> b/Documentation/admin-guide/mm/transhuge.rst
>> index 156a03af0a88..dff8d5985f0f 100644
>> --- a/Documentation/admin-guide/mm/transhuge.rst
>> +++ b/Documentation/admin-guide/mm/transhuge.rst
>> @@ -466,7 +466,7 @@ AnonHugePmdMapped).
>> The number of file transparent huge pages mapped to userspace is
>> available
>> by reading ShmemPmdMapped and ShmemHugePages fields in
>> ``/proc/meminfo``.
>> To identify what applications are mapping file transparent huge
>> pages, it
>> -is necessary to read ``/proc/PID/smaps`` and count the FileHugeMapped
>> fields
>> +is necessary to read ``/proc/PID/smaps`` and count the FilePmdMapped
>> fields
>> for each mapping.
>
> We should probably change the above to clarify that this is all about
> PMD sized things.
Yes, I will create a separate patch to update the document where it
needs to specify that it is for PMD-sized huge page.
> Acked-by: David Hildenbrand <david@redhat.com>
Thanks.
prev parent reply other threads:[~2024-12-18 6:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 8:55 Baolin Wang
2024-12-17 11:59 ` David Hildenbrand
2024-12-18 6:28 ` Baolin Wang [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=2328c2df-fb6c-4c7f-8247-5061b0f94f06@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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