From: Fan Ni <nifan.cxl@gmail.com>
To: Oscar Salvador <osalvador@suse.de>
Cc: nifan.cxl@gmail.com, muchun.song@linux.dev, willy@infradead.org,
mcgrof@kernel.org, a.manzanares@samsung.com, dave@stgolabs.net,
akpm@linux-foundation.org, david@redhat.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/4] mm/hugetlb: Refactor __unmap_hugepage_range() to take folio instead of page
Date: Sun, 4 May 2025 14:35:18 -0700 [thread overview]
Message-ID: <aBfdls-Sw4VpMWQY@lg> (raw)
In-Reply-To: <aBHYK3mqUyvqrGm2@localhost.localdomain>
On Wed, Apr 30, 2025 at 09:58:35AM +0200, Oscar Salvador wrote:
> On Mon, Apr 28, 2025 at 10:11:46AM -0700, nifan.cxl@gmail.com wrote:
> > From: Fan Ni <fan.ni@samsung.com>
> >
> > The function __unmap_hugepage_range() has two kinds of users:
> > 1) unmap_hugepage_range(), which passes in the head page of a folio.
> > Since unmap_hugepage_range() already takes folio and there are no other
> > uses of the folio struct in the function, it is natural for
> > __unmap_hugepage_range() to take folio also.
> > 2) All other uses, which pass in NULL pointer.
> >
> > In both cases, we can pass in folio. Refactor __unmap_hugepage_range() to
> > take folio.
> >
> > Signed-off-by: Fan Ni <fan.ni@samsung.com>
>
> Reviewed-by: Oscar Salvador <osalvador@suse.de>
>
> But:
>
> > void __unmap_hugepage_range(struct mmu_gather *tlb, struct vm_area_struct *vma,
> > unsigned long start, unsigned long end,
> > - struct page *ref_page, zap_flags_t zap_flags)
> > + struct folio *folio, zap_flags_t zap_flags)
>
> I think we are kinda losing information here. ref_ was a good hint
> and...
Hi Oscar,
Thanks for the feedback.
Since the sugguested change here is minor and does not affect the
function, and we do not have a aligned opinion here.
https://lore.kernel.org/linux-mm/b23ef51b-1284-4168-8157-432c3e045788@redhat.com/
I will leave it as it is until there are more pushes for the change.
>
> > struct mm_struct *mm = vma->vm_mm;
> > unsigned long address;
> > @@ -5885,8 +5885,8 @@ void __unmap_hugepage_range(struct mmu_gather *tlb, struct vm_area_struct *vma,
> > * page is being unmapped, not a range. Ensure the page we
> > * are about to unmap is the actual page of interest.
> > */
> > - if (ref_page) {
> > - if (page != ref_page) {
> > + if (folio) {
> > + if (page_folio(page) != folio) {
>
> You have to update the comment above, since we are not passing a
> reference page anymore but a folio.
Will update in the next version. Thanks.
Fan
>
>
>
> --
> Oscar Salvador
> SUSE Labs
>
--
Fan Ni
next prev parent reply other threads:[~2025-05-04 21:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 17:11 [PATCH v3 0/4] mm/hugetlb: Let unmap_hugepage_range() and nifan.cxl
2025-04-28 17:11 ` [PATCH v3 1/4] mm/hugetlb: Pass folio instead of page to unmap_ref_private() nifan.cxl
2025-04-28 20:49 ` David Hildenbrand
2025-04-28 21:02 ` Matthew Wilcox
2025-04-30 7:50 ` Oscar Salvador
2025-04-28 17:11 ` [PATCH v3 2/4] mm/hugetlb: Refactor unmap_hugepage_range() to take folio instead of page nifan.cxl
2025-04-28 20:50 ` David Hildenbrand
2025-04-30 7:52 ` Oscar Salvador
2025-04-28 17:11 ` [PATCH v3 3/4] mm/hugetlb: Refactor __unmap_hugepage_range() " nifan.cxl
2025-04-28 20:51 ` David Hildenbrand
2025-04-30 7:58 ` Oscar Salvador
2025-05-04 21:35 ` Fan Ni [this message]
2025-05-05 7:01 ` David Hildenbrand
2025-04-28 17:11 ` [PATCH v3 4/4] mm/hugetlb: Convert use of struct page to folio in __unmap_hugepage_range() nifan.cxl
2025-04-28 20:53 ` David Hildenbrand
2025-04-30 8:09 ` Oscar Salvador
2025-04-28 19:31 ` [PATCH v3 0/4] mm/hugetlb: Let unmap_hugepage_range() and Andrew Morton
2025-04-28 19:41 ` Fan Ni
2025-04-28 20:54 ` David Hildenbrand
2025-04-28 21:30 ` Fan Ni
2025-04-28 21:01 ` Matthew Wilcox
2025-04-28 21:33 ` Fan Ni
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=aBfdls-Sw4VpMWQY@lg \
--to=nifan.cxl@gmail.com \
--cc=a.manzanares@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=dave@stgolabs.net \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.