linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: lizhe.67@bytedance.com, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, muchun.song@linux.dev,
	David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH v3] vfio/type1: optimize vfio_pin_pages_remote() for huge folio
Date: Tue, 20 May 2025 12:59:47 -0400	[thread overview]
Message-ID: <aCy1AzYFyo4Ma1Z1@x1.local> (raw)
In-Reply-To: <20250520080719.2862017e.alex.williamson@redhat.com>

Hi, Alex,

On Tue, May 20, 2025 at 08:07:19AM -0600, Alex Williamson wrote:
> Peter, David, if you wouldn't mind double checking the folio usage
> here, I'd appreciate it.  The underlying assumption used here is that
> folios always have physically contiguous pages, so we can increment at
> the remainder of the folio_nr_pages() rather than iterate each page.

Yes I think so.  E.g., there's comment above folio definition too:

/**
 * struct folio - Represents a contiguous set of bytes.
 * ...
 * A folio is a physically, virtually and logically contiguous set
 * of bytes...
 */

For 1G, I wonder if in the future vfio can also use memfd_pin_folios()
internally when possible, e.g. after stumbled on top of a hugetlb folio
when filling the batch.

Thanks,

-- 
Peter Xu


  reply	other threads:[~2025-05-20 16:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-20  7:00 [PATCH v3] vfio/type1: optimize vfio_pin_pages_remote() for huge folio lizhe.67
2025-05-20 14:07 ` Alex Williamson
2025-05-20 16:59   ` Peter Xu [this message]
2025-05-20 17:41     ` David Hildenbrand
2025-05-20 21:56       ` Alex Williamson
2025-05-21  3:34   ` lizhe.67
2025-05-20 17:38 ` David Hildenbrand
2025-05-20 22:21   ` Alex Williamson
2025-05-21  6:35     ` David Hildenbrand
2025-05-21 15:40       ` Peter Xu
2025-05-21 16:02         ` David Hildenbrand
2025-05-21 16:55       ` Alex Williamson
2025-05-26 20:19         ` Jason Gunthorpe
2025-05-27 19:52           ` Alex Williamson
2025-05-27 23:46             ` Jason Gunthorpe
2025-05-28 20:09               ` Alex Williamson
2025-05-29  0:51                 ` Jason Gunthorpe
2025-05-29  2:58                   ` Alex Williamson
2025-05-29  4:31                 ` lizhe.67
2025-05-21  3:45   ` lizhe.67
2025-05-20 23:37 ` kernel test robot

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=aCy1AzYFyo4Ma1Z1@x1.local \
    --to=peterx@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=david@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizhe.67@bytedance.com \
    --cc=muchun.song@linux.dev \
    /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).