From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Shivank Garg <shivankg@amd.com>,
akpm@linux-foundation.org, david@redhat.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Cc: ziy@nvidia.com, lorenzo.stoakes@oracle.com,
Liam.Howlett@oracle.com, npache@redhat.com, ryan.roberts@arm.com,
dev.jain@arm.com, fengwei.yin@intel.com, bharata@amd.com
Subject: Re: [PATCH V3 2/2] mm/khugepaged: clean up refcount check using folio_expected_ref_count()
Date: Tue, 27 May 2025 14:26:43 +0800 [thread overview]
Message-ID: <b4d3b436-380a-4f01-8f00-4baaf7ed5a8c@linux.alibaba.com> (raw)
In-Reply-To: <20250526182818.37978-2-shivankg@amd.com>
On 2025/5/27 02:28, Shivank Garg wrote:
> Use folio_expected_ref_count() instead of open-coded logic in
> is_refcount_suitable(). This avoids code duplication and improves
> clarity.
>
> Drop is_refcount_suitable() as it is no longer needed.
>
> Suggested-by: David Hildenbrand <david@redhat.com>
> Acked-by: David Hildenbrand <david@redhat.com>
> Signed-off-by: Shivank Garg <shivankg@amd.com>
Nice cleanup.
Reviewed-by: Baolin Wang <baolin.wang@linux.alibaba.com>
next prev parent reply other threads:[~2025-05-27 6:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 18:28 [PATCH V3 1/2] mm/khugepaged: fix race with folio split/free using temporary reference Shivank Garg
2025-05-26 18:28 ` [PATCH V3 2/2] mm/khugepaged: clean up refcount check using folio_expected_ref_count() Shivank Garg
2025-05-27 3:28 ` Dev Jain
2025-05-27 6:26 ` Baolin Wang [this message]
2025-05-27 3:20 ` [PATCH V3 1/2] mm/khugepaged: fix race with folio split/free using temporary reference Dev Jain
2025-05-27 7:48 ` David Hildenbrand
2025-05-27 8:06 ` Dev Jain
2025-05-27 8:40 ` David Hildenbrand
2025-05-27 8:57 ` Dev Jain
2025-05-27 6:25 ` Baolin Wang
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=b4d3b436-380a-4f01-8f00-4baaf7ed5a8c@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bharata@amd.com \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=fengwei.yin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=npache@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=shivankg@amd.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