From: Ryan Roberts <ryan.roberts@arm.com>
To: Barry Song <21cnbao@gmail.com>,
akpm@linux-foundation.org, linux-mm@kvack.org
Cc: cerasuolodomenico@gmail.com, chrisl@kernel.org, david@redhat.com,
kasong@tencent.com, linux-kernel@vger.kernel.org,
peterx@redhat.com, surenb@google.com, v-songbaohua@oppo.com,
willy@infradead.org, yosryahmed@google.com, yuzhao@google.com,
corbet@lwn.net
Subject: Re: [PATCH v5 4/4] mm: correct the docs for thp_fault_alloc and thp_fault_fallback
Date: Fri, 12 Apr 2024 11:21:06 +0100 [thread overview]
Message-ID: <2eae1247-02dc-47e1-b9b2-317a73937651@arm.com> (raw)
In-Reply-To: <20240412073740.294272-5-21cnbao@gmail.com>
On 12/04/2024 08:37, Barry Song wrote:
> From: Barry Song <v-songbaohua@oppo.com>
>
> The documentation does not align with the code. In
> __do_huge_pmd_anonymous_page(), THP_FAULT_FALLBACK is incremented when
> mem_cgroup_charge() fails, despite the allocation succeeding, whereas
> THP_FAULT_ALLOC is only incremented after a successful charge.
>
> Signed-off-by: Barry Song <v-songbaohua@oppo.com>
> Cc: Chris Li <chrisl@kernel.org>
> Cc: David Hildenbrand <david@redhat.com>
> Cc: Domenico Cerasuolo <cerasuolodomenico@gmail.com>
> Cc: Kairui Song <kasong@tencent.com>
> Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
> Cc: Peter Xu <peterx@redhat.com>
> Cc: Ryan Roberts <ryan.roberts@arm.com>
> Cc: Suren Baghdasaryan <surenb@google.com>
> Cc: Yosry Ahmed <yosryahmed@google.com>
> Cc: Yu Zhao <yuzhao@google.com>
> Cc: Jonathan Corbet <corbet@lwn.net>
Reviewed-by: Ryan Roberts <ryan.roberts@arm.com>
> ---
> Documentation/admin-guide/mm/transhuge.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/admin-guide/mm/transhuge.rst b/Documentation/admin-guide/mm/transhuge.rst
> index f436ff982f22..98e3a99ea780 100644
> --- a/Documentation/admin-guide/mm/transhuge.rst
> +++ b/Documentation/admin-guide/mm/transhuge.rst
> @@ -369,7 +369,7 @@ monitor how successfully the system is providing huge pages for use.
>
> thp_fault_alloc
> is incremented every time a huge page is successfully
> - allocated to handle a page fault.
> + allocated and charged to handle a page fault.
>
> thp_collapse_alloc
> is incremented by khugepaged when it has found
> @@ -377,7 +377,7 @@ thp_collapse_alloc
> successfully allocated a new huge page to store the data.
>
> thp_fault_fallback
> - is incremented if a page fault fails to allocate
> + is incremented if a page fault fails to allocate or charge
> a huge page and instead falls back to using small pages.
>
> thp_fault_fallback_charge
prev parent reply other threads:[~2024-04-12 10:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 7:37 [PATCH v5 0/4] mm: add per-order mTHP alloc and swpout counters Barry Song
2024-04-12 7:37 ` [PATCH v5 1/4] mm: add per-order mTHP anon_fault_alloc and anon_fault_fallback counters Barry Song
2024-04-12 9:26 ` Ryan Roberts
2024-04-12 9:43 ` Barry Song
2024-04-12 9:56 ` Ryan Roberts
2024-04-12 10:17 ` Barry Song
2024-04-12 10:25 ` Ryan Roberts
2024-04-12 10:29 ` Barry Song
2024-04-12 10:38 ` Ryan Roberts
2024-04-12 10:53 ` Barry Song
2024-04-12 11:05 ` Ryan Roberts
2024-04-12 7:37 ` [PATCH v5 2/4] mm: add per-order mTHP anon_swpout and anon_swpout_fallback counters Barry Song
2024-04-12 9:43 ` Ryan Roberts
2024-04-12 7:37 ` [PATCH v5 3/4] mm: add docs for per-order mTHP counters and transhuge_page ABI Barry Song
2024-04-12 10:19 ` Ryan Roberts
2024-04-12 7:37 ` [PATCH v5 4/4] mm: correct the docs for thp_fault_alloc and thp_fault_fallback Barry Song
2024-04-12 10:21 ` 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=2eae1247-02dc-47e1-b9b2-317a73937651@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=corbet@lwn.net \
--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;
as well as URLs for NNTP newsgroup(s).