Linux NFS development
 help / color / mirror / Atom feed
From: Pranjal Shrivastava <praan@google.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	Trond Myklebust <trondmy@kernel.org>,
	Anna Schumaker <anna@kernel.org>, Christoph Hellwig <hch@lst.de>,
	Shivaji Kant <shivajikant@google.com>
Subject: Re: [PATCH v2 0/7] nfs: Modernize Direct I/O path
Date: Fri, 19 Jun 2026 11:48:37 +0000	[thread overview]
Message-ID: <ajUslaUwTClnFve_@google.com> (raw)
In-Reply-To: <ajP8oV7Ho3db_09N@infradead.org>

On Thu, Jun 18, 2026 at 07:11:45AM -0700, Christoph Hellwig wrote:

Hi Christoph,

> On Tue, Jun 16, 2026 at 01:39:53PM +0000, Pranjal Shrivastava wrote:
> > =======
> > This series has been tested with xfstests [2] on RDMA & TCP transports:
> > 
> >  ./check generic/091 generic/130 generic/139 generic/143 generic/154 \
> >          generic/155 generic/183 generic/188 generic/190 generic/196 \
> >          generic/198 generic/203 generic/214 generic/240 generic/263 \
> >          generic/287 generic/290 generic/292 generic/330 generic/444 \
> >          generic/450 generic/451 generic/586 generic/647 generic/708 \
> >          generic/729 generic/760
> 
> Did you only run these tests that previously failed for Anna or all
> of xfstests, which should give you much better coverage?

I highlighted those specific tests in the cover letter as they were
reported as failures for the NFS direct I/O path.

I've also run the full xfstests quick group on both the unpatched and
patched kernels (7.1-rc7) across RDMA and TCP transports. I did not see
any regressions between the two runs, the results were identical across
the quick suite.

I could report the entire run for a patched and unpatched kernel in the
v3 cover letter if you'd like?

Thanks,
Praan

      reply	other threads:[~2026-06-19 11:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-16 13:39 [PATCH v2 0/7] nfs: Modernize Direct I/O path Pranjal Shrivastava
2026-06-16 13:39 ` [PATCH v2 1/7] nfs: make nfs_page pin-aware Pranjal Shrivastava
2026-06-16 13:39 ` [PATCH v2 2/7] nfs: Track number of pinned pages in nfs_page Pranjal Shrivastava
2026-06-16 13:39 ` [PATCH v2 3/7] nfs: Introduce nfs_release_request_list helper Pranjal Shrivastava
2026-06-16 13:39 ` [PATCH v2 4/7] nfs: migrate direct I/O to iov_iter_extract_pages Pranjal Shrivastava
2026-06-16 13:39 ` [PATCH v2 5/7] nfs: introduce nfs_direct_extract_pages helper Pranjal Shrivastava
2026-06-16 13:39 ` [PATCH v2 6/7] nfs: Optimize direct I/O to use folios for requests Pranjal Shrivastava
2026-06-16 15:29   ` Trond Myklebust
2026-06-16 17:23     ` Pranjal Shrivastava
2026-06-18 14:10       ` Christoph Hellwig
2026-06-18 18:20         ` Matthew Wilcox
2026-06-19 12:32           ` Pranjal Shrivastava
2026-06-16 13:40 ` [PATCH v2 7/7] nfs: Cleanup the nfs_page_create_from_page helper Pranjal Shrivastava
2026-06-16 14:15 ` [PATCH v2 0/7] nfs: Modernize Direct I/O path Pranjal Shrivastava
2026-06-18 13:46 ` Chuck Lever
2026-06-19 11:50   ` Pranjal Shrivastava
2026-06-18 14:11 ` Christoph Hellwig
2026-06-19 11:48   ` 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=ajUslaUwTClnFve_@google.com \
    --to=praan@google.com \
    --cc=anna@kernel.org \
    --cc=hch@infradead.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox