All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pranjal Shrivastava <praan@google.com>
To: linux-nfs@vger.kernel.org, Trond Myklebust <trondmy@kernel.org>,
	Anna Schumaker <anna@kernel.org>
Cc: 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 v4 0/5] nfs: modernize direct I/O path
Date: Mon, 10 Aug 2026 20:38:49 +0000	[thread overview]
Message-ID: <ano2R8fAeGmsNt9f@google.com> (raw)
In-Reply-To: <20260810195040.2877784-1-praan@google.com>

On Mon, Aug 10, 2026 at 07:50:34PM +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.
> 

[...]

I'm calling out a few typos / non-code mistakes:

1. On the cover letter I missed updating the subject to v5 for this series
  (the changelog is noted below).

2. I also accidentally dropped Christoph's Reviewed-by tags on patches 
   1, 2, and 3 during the rebase (given while reviewing v4 [1]).

Everything else in the series is correct as per the v5 changelog.
Please let me know what the right etiquette is? Shall I resend the series?

Apologies for the noise!

> 
> [v5]
>  - Fixed an iov_iter_revert oops in nfs_direct_extract_pages().
>  - Fixed a refcount underflow in nfs_direct_release_pages() during
>    swap-over-NFS by ensuring we do not call put_page() on unpinned memory.
>  - Rebased on fs-next
> 
> [v4]
>  - https://lore.kernel.org/all/20260720150601.2702700-1-praan@google.com/
>  - Dropped superfluous externs in include/linux/nfs_page.h
>  - Scoped `req` locally inside the loop in nfs_release_request_list()
>  - Wrapped >80 character lines in Patch 1 to adhere to coding style.
>  - Fixed typos and capitalization convention in the commit msgs
>  - Collected Reviewed-by tags from Christoph and Shivaji
>  - Rebased on fs-next
> 
> [v3]
>  - https://lore.kernel.org/all/20260715143540.3597616-1-praan@google.com/
>  - Dropped patches that added folio support for NFS Direct I/O
>  - Folded requested_bytes accounting in patch 5 due to dropped folio support
>  - Rebased on fs-next
> 
> [v2] 
>  - https://lore.kernel.org/all/20260616134000.2733403-1-praan@google.com/
>  - Fix data corruption in nfs_direct_extract_pages() by correctly
>    calculating intra-page offsets using offset_in_page().
>  - Fix requested_bytes accounting in direct read/write paths to only
>    increment after successful RPC scheduling.
>  - Add missing kernel-doc descriptions for the @pinned parameter in
>    nfs_page_create_from_page() and nfs_page_create_from_folio().
>  - Rebase on fs-next/
> 
> [v1] https://lore.kernel.org/all/20260603053033.3300318-1-praan@google.com/
> 
> Pranjal Shrivastava (5):
>   nfs: make nfs_page pin-aware
>   nfs: track number of pinned pages in nfs_page
>   nfs: introduce nfs_release_request_list helper
>   nfs: migrate direct I/O to iov_iter_extract_pages
>   nfs: introduce nfs_direct_extract_pages helper
> 
>  fs/nfs/direct.c          | 139 ++++++++++++++++++++-------------------
>  fs/nfs/pagelist.c        |  62 ++++++++++++++---
>  fs/nfs/read.c            |   2 +-
>  fs/nfs/write.c           |   2 +-
>  include/linux/nfs_page.h |   8 ++-
>  5 files changed, 130 insertions(+), 83 deletions(-)
> 
> 
> base-commit: 5b57716ed7ad2f4b1724461c8777015c4e4befb1
> -- 
> 2.55.0.679.g6767b8d81c-goog
> 

Thanks,
Praan

[1] https://lore.kernel.org/all/20260720150601.2702700-1-praan@google.com/


  parent reply	other threads:[~2026-08-10 20:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-10 19:50 [PATCH v4 0/5] nfs: modernize direct I/O path Pranjal Shrivastava
2026-08-10 19:50 ` [PATCH v5 1/5] nfs: make nfs_page pin-aware Pranjal Shrivastava
2026-08-10 19:50 ` [PATCH v5 2/5] nfs: track number of pinned pages in nfs_page Pranjal Shrivastava
2026-08-10 19:50 ` [PATCH v5 3/5] nfs: introduce nfs_release_request_list helper Pranjal Shrivastava
2026-08-10 19:50 ` [PATCH v5 4/5] nfs: migrate direct I/O to iov_iter_extract_pages Pranjal Shrivastava
2026-08-10 19:50 ` [PATCH v5 5/5] nfs: introduce nfs_direct_extract_pages helper Pranjal Shrivastava
2026-08-10 20:38 ` Pranjal Shrivastava [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-07-20 15:05 [PATCH v4 0/5] nfs: modernize direct I/O path Pranjal Shrivastava

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=ano2R8fAeGmsNt9f@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.