From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Sarthak Sharma <sarthak.sharma@arm.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
John Hubbard <jhubbard@nvidia.com>, Peter Xu <peterx@redhat.com>,
Kiryl Shutsemau <kas@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mm/gup_test: report actual pinned bytes
Date: Mon, 7 Sep 2026 15:44:21 +0200 [thread overview]
Message-ID: <d35a4da9-aed6-4b25-8a6b-2ffaf5263009@kernel.org> (raw)
In-Reply-To: <20260831101304.162867-1-sarthak.sharma@arm.com>
On 8/31/26 12:13, Sarthak Sharma wrote:
> __gup_test_ioctl() advances addr to the end of the current batch before
> checking if GUP pinned the entire requested batch. If GUP pins more than
> 0 pages but less than the requested batch size, addr still advances by
> the requested batch size.
>
> The next iteration detects the partial pinning and breaks out of the loop.
> Again gup->size is calculated using addr - gup->addr, so it also includes
> the unpinned pages of the requested batch.
>
> Calculate gup->size using the actual number of pages pinned multiplied
> by PAGE_SIZE.
>
> Fixes: 64c349f4ae78 ("mm: add infrastructure for get_user_pages_fast() benchmarking")
> Reviewed-by: Kiryl Shutsemau (Meta) <kas@kernel.org>
> Signed-off-by: Sarthak Sharma <sarthak.sharma@arm.com>
> ---
> Changes in v2:
> - Fix typo in the commit message
>
> v1: lore.kernel.org/all/20260831064808.77768-1-sarthak.sharma@arm.com/
>
> mm/gup_test.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/gup_test.c b/mm/gup_test.c
> index 44c1cdfb9c37..185ba3bb8ed1 100644
> --- a/mm/gup_test.c
> +++ b/mm/gup_test.c
> @@ -188,7 +188,7 @@ static int __gup_test_ioctl(unsigned int cmd,
> nr_pages = i;
>
> gup->get_delta_usec = ktime_us_delta(end_time, start_time);
> - gup->size = addr - gup->addr;
> + gup->size = nr_pages * PAGE_SIZE;
>
> /*
> * Take an un-benchmark-timed moment to verify DMA pinned
Acked-by: David Hildenbrand (Arm) <david@kernel.org>
I assume that loop handling could get cleaned up a bit.
--
Cheers,
David
prev parent reply other threads:[~2026-09-07 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 10:13 Sarthak Sharma
2026-09-01 0:12 ` Andrew Morton
2026-09-07 13:44 ` David Hildenbrand (Arm) [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=d35a4da9-aed6-4b25-8a6b-2ffaf5263009@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=kas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.com \
--cc=sarthak.sharma@arm.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
all inboxes | Powered by JetHome®