Re: [PATCH v6 0/5] nfs: modernize direct I/O path

[Anna Schumaker]

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

>
> [...]
>
>> 
>> [v6]
>>  - Fixed double unpin bugs pointed out by Sashiko:
>>    https://sashiko.dev/#/patchset/20260810195040.2877784-1-praan%40google.com
>>  - Added R-bs from Christoph (due since v4)
>> 
>> [v5]
>>  - https://lore.kernel.org/all/20260810195040.2877784-1-praan@xxxxxxxxxx/
>>  - 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
>> 
>
> [...]
>
> Thanks,
> Praan