From: Yuan-Hao Hsu <aa9736195201@gmail.com>
To: David Hildenbrand <david@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jason Gunthorpe <jgg@ziepe.ca>,
John Hubbard <jhubbard@nvidia.com>, Peter Xu <peterx@redhat.com>,
Lorenzo Stoakes <ljs@kernel.org>,
liam@infradead.org, Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>, Rik van Riel <riel@surriel.com>,
Aristeu Rozanski <aris@ruivo.org>,
Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/gup: batch PTE-mapped large folios in gup_fast_pte_range()
Date: Thu, 17 Sep 2026 17:01:14 +0800 [thread overview]
Message-ID: <20260917090114.611-1-aa9736195201@gmail.com> (raw)
In-Reply-To: <e988b0e8-3ee9-45ed-9d34-7b73d86d9cfd@kernel.org>
On Thu, 17 Sep 2026 10:43:22 +0200, David Hildenbrand (Arm) wrote:
> Ah, no, Rik looked at GUP not GUP-fast. So I'll have a look but it will take a
> while.
Thanks.
One note for whenever you get to it: the patch is against mainline, and
the last hunk has a two-line context conflict with Aristeu's
gup_fast_*() cleanup in mm-everything (pages[nr_pages++] there). I
have the same change on top of mm-everything-2026-09-15-07-39 if that
base is preferable, and can post FPB_LOCKLESS as a separate first patch
if a two-patch series is easier to review.
Yuan-Hao Hsu
next prev parent reply other threads:[~2026-09-17 9:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 8:37 [PATCH] mm/gup: batch PTE-mapped large folios in gup_fast_pte_range() Yuan-Hao Hsu
2026-09-17 8:42 ` David Hildenbrand (Arm)
2026-09-17 8:43 ` David Hildenbrand (Arm)
2026-09-17 9:01 ` Yuan-Hao Hsu [this message]
2026-10-07 10:07 ` Rik van Riel
2026-10-07 10:14 ` David Hildenbrand (Arm)
2026-10-07 10:47 ` Rik van Riel
2026-10-10 19:52 ` Yuan-Hao Hsu
2026-10-12 17:58 ` Rik van Riel
2026-10-12 19:05 ` David Hildenbrand (Arm)
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=20260917090114.611-1-aa9736195201@gmail.com \
--to=aa9736195201@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aris@ruivo.org \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=peterx@redhat.com \
--cc=riel@surriel.com \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=surenb@google.com \
--cc=vbabka@kernel.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.