From: Dave Wysochanski <dwysocha@redhat.com>
To: Trond Myklebust <trondmy@hammerspace.com>,
Anna Schumaker <anna.schumaker@netapp.com>
Cc: Matthew Wilcox <willy@infradead.org>,
David Howells <dhowells@redhat.com>,
Chuck Lever <chuck.lever@oracle.com>,
linux-cachefs@redhat.com, linux-nfs@vger.kernel.org
Subject: [PATCH 0/1] Convert nfs_readpages() to nfs_readahead()
Date: Thu, 7 Oct 2021 19:32:07 -0400 [thread overview]
Message-ID: <1633649528-1321-1-git-send-email-dwysocha@redhat.com> (raw)
This patch converts nfs_readpages() to nfs_readahead(). It was
applied on top of the set I just posted [1] plus Chuck's v1 patch to
convert dfprintks to tracepoints [2]. It is being tested on top of
these patches at BakeAThon against various servers, cthon, xfstests,
and my fscache unit tests. Note that Chuck may post a v3 of his
patch and this would need rebased on that patch.
Note that a nfs-utils patch will need to be done to properly account
for the changed NFSIOS_* counters.
I would consider this a "nice to have" for this cycle but I wanted
to get it out there sooner than later. As far as I know this has
been an outstanding item for the NFS client for a while and the
fscache fallback IO API clears the way for this patch.
[1] https://marc.info/?l=linux-nfs&m=163364580324243&w=2
[2] https://marc.info/?l=linux-nfs&m=163345402812426&w=2
Dave Wysochanski (1):
NFS: Convert from readpages() to readahead()
fs/nfs/file.c | 2 +-
fs/nfs/nfstrace.h | 2 +-
fs/nfs/read.c | 21 +++++++++++++++------
include/linux/nfs_fs.h | 3 +--
include/linux/nfs_iostat.h | 6 +++---
5 files changed, 21 insertions(+), 13 deletions(-)
--
1.8.3.1
next reply other threads:[~2021-10-07 23:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 23:32 Dave Wysochanski [this message]
2021-10-07 23:32 ` [PATCH 1/1] NFS: Convert from readpages() to readahead() Dave Wysochanski
2021-10-08 14:09 ` Chuck Lever III
2021-10-09 12:35 ` David Wysochanski
2021-10-09 13:42 ` David Wysochanski
2021-10-15 7:42 ` Trond Myklebust
2021-10-15 20:18 ` Chuck Lever III
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=1633649528-1321-1-git-send-email-dwysocha@redhat.com \
--to=dwysocha@redhat.com \
--cc=anna.schumaker@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=dhowells@redhat.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@hammerspace.com \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).