From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Zi Yan <ziy@nvidia.com>
Cc: Balbir Singh <balbirs@nvidia.com>,
David Hildenbrand <david@redhat.com>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hughd@google.com>,
Kirill Shutemov <k.shutemov@gmail.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Nico Pache <npache@redhat.com>,
Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
Barry Song <baohua@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] mm/huge_memory: use folio_expected_ref_count() to calculate ref_count.
Date: Thu, 17 Jul 2025 15:31:03 +0100 [thread overview]
Message-ID: <1c125a8e-650d-46fd-aff5-0cbf81cd8474@lucifer.local> (raw)
In-Reply-To: <20250714171823.3626213-3-ziy@nvidia.com>
On Mon, Jul 14, 2025 at 01:18:23PM -0400, Zi Yan wrote:
> Instead of open coding the ref_count calculation, use
> folio_expected_ref_count().
You really should put something here about why it is that the open-coded
value and the value returned from folio_expected_ref_count() would be
expected to be the same. See comment below inline with code.
>
> Suggested-by: David Hildenbrand <david@redhat.com>
> Signed-off-by: Zi Yan <ziy@nvidia.com>
> Acked-by: Balbir Singh <balbirs@nvidia.com>
> Acked-by: David Hildenbrand <david@redhat.com>
Ah haha you're literally addresing some of my code review here from the
last patch :) I love it when that happens :P
I'd like you to improve the commit message, but that's a nit so:
Reviewed-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
See below for some analysis of the folio_expected_ref_count().
> ---
> mm/huge_memory.c | 12 +++++-------
> 1 file changed, 5 insertions(+), 7 deletions(-)
>
> diff --git a/mm/huge_memory.c b/mm/huge_memory.c
> index a7ee731f974f..31b5c4e61a57 100644
> --- a/mm/huge_memory.c
> +++ b/mm/huge_memory.c
> @@ -3735,6 +3735,7 @@ static int __folio_split(struct folio *folio, unsigned int new_order,
> if (folio_ref_freeze(folio, 1 + extra_pins)) {
> struct address_space *swap_cache = NULL;
> struct lruvec *lruvec;
> + int expected_refs;
>
> if (folio_order(folio) > 1 &&
> !list_empty(&folio->_deferred_list)) {
> @@ -3805,11 +3806,8 @@ static int __folio_split(struct folio *folio, unsigned int new_order,
> new_folio = next) {
> next = folio_next(new_folio);
>
> - folio_ref_unfreeze(
> - new_folio,
> - 1 + ((mapping || swap_cache) ?
> - folio_nr_pages(new_folio) :
> - 0));
> + expected_refs = folio_expected_ref_count(new_folio) + 1;
So digging in:
static inline int folio_expected_ref_count(const struct folio *folio)
{
const int order = folio_order(folio);
int ref_count = 0;
...
if (folio_test_anon(folio)) {
/* One reference per page from the swapcache. */
ref_count += folio_test_swapcache(folio) << order;
} else {
/* One reference per page from the pagecache. */
ref_count += !!folio->mapping << order;
^---- these are covered off by (mapping || swap_cache) ? folio_nr_pages(folio)
/* One reference from PG_private. */
ref_count += folio_test_private(folio);
This one is trickier.
OK so looking through the logic, the can_split_folio() function will
already assert that the only pins you have are the swapcache/page cache
ones on the 'origin' folio (the mapcount bit used in the freeze doesn't matter
as you're dealing with split, not-yet-mapped 'sub'-folios).
So this precludes an elevated refcount from PG_private, therefore this will
naturally be 0.
}
/* One reference per page table mapping. */
return ref_count + folio_mapcount(folio);
folio_mapcount() will be zero for these split folios, until remapped.
}
You add the + 1 to account for the folio pin of course.
TL;DR - this is correct AFAICT.
> + folio_ref_unfreeze(new_folio, expected_refs);
>
> lru_add_split_folio(folio, new_folio, lruvec, list);
>
> @@ -3839,8 +3837,8 @@ static int __folio_split(struct folio *folio, unsigned int new_order,
> * Otherwise, a parallel folio_try_get() can grab origin_folio
> * and its caller can see stale page cache entries.
> */
> - folio_ref_unfreeze(folio, 1 +
> - ((mapping || swap_cache) ? folio_nr_pages(folio) : 0));
> + expected_refs = folio_expected_ref_count(folio) + 1;
> + folio_ref_unfreeze(folio, expected_refs);
>
> unlock_page_lruvec(lruvec);
>
> --
> 2.47.2
>
next prev parent reply other threads:[~2025-07-17 14:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 17:18 [PATCH v3 0/2] __folio_split() clean up Zi Yan
2025-07-14 17:18 ` [PATCH v3 1/2] mm/huge_memory: move unrelated code out of __split_unmapped_folio() Zi Yan
2025-07-14 18:54 ` David Hildenbrand
2025-07-17 14:07 ` Lorenzo Stoakes
2025-07-17 15:41 ` Zi Yan
2025-07-17 17:44 ` Lorenzo Stoakes
2025-07-17 18:05 ` Zi Yan
2025-07-17 18:07 ` Lorenzo Stoakes
2025-07-14 17:18 ` [PATCH v3 2/2] mm/huge_memory: use folio_expected_ref_count() to calculate ref_count Zi Yan
2025-07-17 8:03 ` Baolin Wang
2025-07-17 14:31 ` Lorenzo Stoakes [this message]
2025-07-17 12:40 ` [PATCH v3 0/2] __folio_split() clean up Lorenzo Stoakes
2025-07-17 15:54 ` Zi Yan
2025-07-17 17:39 ` Lorenzo Stoakes
2025-07-17 22:35 ` Andrew Morton
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=1c125a8e-650d-46fd-aff5-0cbf81cd8474@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=balbirs@nvidia.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=hughd@google.com \
--cc=k.shutemov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npache@redhat.com \
--cc=ryan.roberts@arm.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