All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Steve Sistare <steven.sistare@oracle.com>
Cc: iommu@lists.linux.dev, Kevin Tian <kevin.tian@intel.com>,
	Nicolin Chen <nicolinc@nvidia.com>
Subject: Re: [PATCH V4 6/9] iommufd: pfn reader for file mappings
Date: Mon, 21 Oct 2024 14:32:26 -0300	[thread overview]
Message-ID: <20241021173226.GD13034@nvidia.com> (raw)
In-Reply-To: <1729286856-127844-7-git-send-email-steven.sistare@oracle.com>

On Fri, Oct 18, 2024 at 02:27:33PM -0700, Steve Sistare wrote:

> +static long pin_memfd_pages(struct pfn_reader_user *user, unsigned long start,
> +			    unsigned long npages)
> +{
> +	unsigned long i;
> +	unsigned long j;
> +	unsigned long offset;
> +	unsigned long npages_out = 0;
> +	struct page **upages = user->upages;
> +	unsigned long end = start + (npages << PAGE_SHIFT) - 1;
> +	long nfolios = user->ufolios_len / sizeof(*user->ufolios);
> +
> +	nfolios = memfd_pin_folios(user->file, start, end, user->ufolios,
> +				   nfolios, &offset);
> +	if (nfolios <= 0)
> +		return nfolios;
> +
> +	offset >>= PAGE_SHIFT;
> +	user->ufolios_next = user->ufolios;
> +	user->ufolios_offset = offset;
> +
> +	for (i = 0; i < nfolios; i++) {
> +		struct folio *folio = user->ufolios[i];
> +		unsigned long nr = folio_nr_pages(folio);
> +		unsigned long npin = min(nr - offset, npages);

Let's add a comment note about the loop computing npages being able to be
optimized someday

But I think this looks good, with the add_refs change you noted

Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>

> +		if (upages)
> +			for (j = offset; j < offset + npin; j++)
> +				*upages++ = folio_page(folio, j);

The upages path is 'slow' and rarely used because it is for mdevs
only, so it would be fine if it was the only loop here.

Jason

  parent reply	other threads:[~2024-10-21 17:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18 21:27 [PATCH V4 0/9] iommu_ioas_map_file Steve Sistare
2024-10-18 21:27 ` [PATCH V4 1/9] mm/gup: folio_add_pins Steve Sistare
2024-10-18 21:27 ` [PATCH V4 2/9] iommufd: rename uptr in iopt_alloc_iova Steve Sistare
2024-10-22 18:32   ` Nicolin Chen
2024-10-18 21:27 ` [PATCH V4 3/9] iommufd: generalize iopt_pages address Steve Sistare
2024-10-22 18:38   ` Nicolin Chen
2024-10-18 21:27 ` [PATCH V4 4/9] iommufd: pfn reader local variables Steve Sistare
2024-10-18 21:27 ` [PATCH V4 5/9] iommufd: folio subroutines Steve Sistare
2024-10-21 17:30   ` Jason Gunthorpe
2024-10-22 13:26     ` Steven Sistare
2024-10-18 21:27 ` [PATCH V4 6/9] iommufd: pfn reader for file mappings Steve Sistare
2024-10-19 18:41   ` kernel test robot
2024-10-21 17:32   ` Jason Gunthorpe [this message]
2024-10-18 21:27 ` [PATCH V4 7/9] iommufd: IOMMU_IOAS_MAP_FILE Steve Sistare
2024-10-21 17:34   ` Jason Gunthorpe
2024-10-18 21:27 ` [PATCH V4 8/9] iommufd: file mappings for mdev Steve Sistare
2024-10-18 21:27 ` [PATCH V4 9/9] iommufd: map file selftest Steve Sistare
2024-10-18 22:51   ` Nicolin Chen
2024-10-22 13:27     ` Steven Sistare

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=20241021173226.GD13034@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=iommu@lists.linux.dev \
    --cc=kevin.tian@intel.com \
    --cc=nicolinc@nvidia.com \
    --cc=steven.sistare@oracle.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 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.