From: Pranjal Shrivastava <praan@google.com>
To: Anna Schumaker <anna@kernel.org>
Cc: linux-nfs@vger.kernel.org, Trond Myklebust <trondmy@kernel.org>,
Chuck Lever <cel@kernel.org>, Jeff Layton <jlayton@kernel.org>,
linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Logan Gunthorpe <logang@deltatee.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
linux-pci@vger.kernel.org, linux-rdma@vger.kernel.org,
Shivaji Kant <shivajikant@google.com>
Subject: Re: [PATCH v6 0/5] nfs: modernize direct I/O path
Date: Sun, 13 Sep 2026 19:07:38 +0000 [thread overview]
Message-ID: <aqb0ejwzD8citck6@google.com> (raw)
In-Reply-To: <0b3d8f13-e691-411a-a507-d3e6bd1608c6@app.fastmail.com>
On Fri, Sep 11, 2026 at 10:41:57AM -0400, Anna Schumaker wrote:
> Hi Pranjal,
>
> On Fri, Sep 11, 2026, at 8:57 AM, Pranjal Shrivastava wrote:
> > On Fri, Aug 14, 2026 at 02:32:50PM +0000, Pranjal Shrivastava wrote:
> >> Modernize the NFS Direct I/O path as a preparatory step to enable PCI
> >> Peer-to-Peer DMA (P2PDMA) support. Following feedback on the initial
> >> RFC [1], the modernization and architectural changes are split into
> >> different series. Additionally, based on the discussion in the v2 [2]
> >> of this series, the migration of NFS Direct I/O to folios would be
> >> handled in a separate follow-up series.
> >>
> >> Currently, NFS O_DIRECT relies on the legacy iov_iter_get_pages_alloc2()
> >> API which does not support the pinning requirements for P2P memory.
> >> The implementation moves NFS to the modern iov_iter_extract_pages() API.
> >>
> >
> > Gentle ping on this series.
> > (I realized that I sent it close to the merge window, Apologies).
> >
> > Please let me know if anything else needs to be done for this..
>
> Thanks for the ping! The plan right now is to send it along as part of
> the 7.4 merge window. I haven't pushed out a public linux-next branch
> yet, but when I do these patches will be included.
>
> I hope this helps!
> Anna
>
Thanks a lot for responding, quite helpful! :)
Best,
Praan
prev parent reply other threads:[~2026-09-13 19:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 14:32 [PATCH v6 0/5] nfs: modernize direct I/O path Pranjal Shrivastava
2026-08-14 14:32 ` [PATCH v6 1/5] nfs: make nfs_page pin-aware Pranjal Shrivastava
2026-08-14 14:46 ` sashiko-bot
2026-08-14 15:04 ` Pranjal Shrivastava
2026-08-14 14:32 ` [PATCH v6 2/5] nfs: track number of pinned pages in nfs_page Pranjal Shrivastava
2026-08-14 14:47 ` sashiko-bot
2026-08-14 15:14 ` Pranjal Shrivastava
2026-08-14 14:32 ` [PATCH v6 3/5] nfs: introduce nfs_release_request_list helper Pranjal Shrivastava
2026-08-14 14:38 ` sashiko-bot
2026-08-14 14:32 ` [PATCH v6 4/5] nfs: migrate direct I/O to iov_iter_extract_pages Pranjal Shrivastava
2026-08-14 14:48 ` sashiko-bot
2026-08-14 14:32 ` [PATCH v6 5/5] nfs: introduce nfs_direct_extract_pages helper Pranjal Shrivastava
2026-08-14 14:40 ` sashiko-bot
2026-09-11 12:57 ` [PATCH v6 0/5] nfs: modernize direct I/O path Pranjal Shrivastava
2026-09-11 14:41 ` Anna Schumaker
2026-09-13 19:07 ` Pranjal Shrivastava [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=aqb0ejwzD8citck6@google.com \
--to=praan@google.com \
--cc=anna@kernel.org \
--cc=cel@kernel.org \
--cc=hch@lst.de \
--cc=jgg@ziepe.ca \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=shivajikant@google.com \
--cc=trondmy@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.