From: Alex Williamson <alex.williamson@redhat.com>
To: lizhe.67@bytedance.com
Cc: jgg@ziepe.ca, david@redhat.com, peterx@redhat.com,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/3] vfio/type1: batch vfio_find_vpfn() in function vfio_unpin_pages_remote()
Date: Fri, 27 Jun 2025 15:40:59 -0600 [thread overview]
Message-ID: <20250627154059.0e134073.alex.williamson@redhat.com> (raw)
In-Reply-To: <20250620032344.13382-2-lizhe.67@bytedance.com>
On Fri, 20 Jun 2025 11:23:42 +0800
lizhe.67@bytedance.com wrote:
> From: Li Zhe <lizhe.67@bytedance.com>
>
> This patch is based on patch 'vfio/type1: optimize
> vfio_pin_pages_remote() for large folios'[1].
The above and the below link are only necessary in the cover letter, or
below the --- marker below, they don't really make sense in the
committed log.
Anyway, aside from that and one nit on 2/ (sent separately), the series
looks ok to me and I hope David and Jason will chime in with A-b/R-b
give the previous discussions.
Given the build bot error[1] I'd suggest resending all your work in a
single series, the previous map optimization and the unmap optimization
here. That way the dependency is already included, and it's a good
nudge for acks. Thanks,
Alex
[1]https://lore.kernel.org/all/202506250037.VfdBAPP3-lkp@intel.com/
>
> The function vpfn_pages() can help us determine the number of vpfn
> nodes on the vpfn rb tree within a specified range. This allows us
> to avoid searching for each vpfn individually in the function
> vfio_unpin_pages_remote(). This patch batches the vfio_find_vpfn()
> calls in function vfio_unpin_pages_remote().
>
> [1]: https://lore.kernel.org/all/20250529064947.38433-1-lizhe.67@bytedance.com/
>
> Signed-off-by: Li Zhe <lizhe.67@bytedance.com>
> ---
> drivers/vfio/vfio_iommu_type1.c | 10 +++-------
> 1 file changed, 3 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/vfio/vfio_iommu_type1.c b/drivers/vfio/vfio_iommu_type1.c
> index 28ee4b8d39ae..e952bf8bdfab 100644
> --- a/drivers/vfio/vfio_iommu_type1.c
> +++ b/drivers/vfio/vfio_iommu_type1.c
> @@ -805,16 +805,12 @@ static long vfio_unpin_pages_remote(struct vfio_dma *dma, dma_addr_t iova,
> unsigned long pfn, unsigned long npage,
> bool do_accounting)
> {
> - long unlocked = 0, locked = 0;
> + long unlocked = 0, locked = vpfn_pages(dma, iova, npage);
> long i;
>
> - for (i = 0; i < npage; i++, iova += PAGE_SIZE) {
> - if (put_pfn(pfn++, dma->prot)) {
> + for (i = 0; i < npage; i++)
> + if (put_pfn(pfn++, dma->prot))
> unlocked++;
> - if (vfio_find_vpfn(dma, iova))
> - locked++;
> - }
> - }
>
> if (do_accounting)
> vfio_lock_acct(dma, locked - unlocked, true);
next prev parent reply other threads:[~2025-06-27 21:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 3:23 [PATCH v5 0/3] vfio/type1: optimize vfio_unpin_pages_remote() for large folio lizhe.67
2025-06-20 3:23 ` [PATCH v5 1/3] vfio/type1: batch vfio_find_vpfn() in function vfio_unpin_pages_remote() lizhe.67
2025-06-24 16:23 ` kernel test robot
2025-06-25 2:29 ` lizhe.67
2025-06-27 21:40 ` Alex Williamson [this message]
2025-06-30 2:45 ` lizhe.67
2025-06-20 3:23 ` [PATCH v5 2/3] vfio/type1: introduce a new member has_rsvd for struct vfio_dma lizhe.67
2025-06-27 21:40 ` Alex Williamson
2025-06-20 3:23 ` [PATCH v5 3/3] vfio/type1: optimize vfio_unpin_pages_remote() for large folio lizhe.67
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=20250627154059.0e134073.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=david@redhat.com \
--cc=jgg@ziepe.ca \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhe.67@bytedance.com \
--cc=peterx@redhat.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;
as well as URLs for NNTP newsgroup(s).