From: trondmy@kernel.org
To: Anna Schumaker <anna.schumaker@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/4] pNFS/flexfiles: Cancel I/O if the layout is revoked
Date: Wed, 5 Oct 2022 15:57:34 -0400 [thread overview]
Message-ID: <20221005195738.4552-1-trondmy@kernel.org> (raw)
From: Trond Myklebust <trond.myklebust@hammerspace.com>
The pNFS/flexfiles driver is capable of having a lot of outstanding I/O
in the RPC layer when it flushes out the writeback data. If the server
decides to recall or revoke the layout when this happens, then it takes
a while for that I/O to complete.
To speed things up, add an API to allow the flexfiles driver to cancel
that I/O and hence return the layout earlier.
Trond Myklebust (4):
SUNRPC: Fix races with rpc_killall_tasks()
SUNRPC: Add a helper to allow pNFS drivers to selectively cancel RPC
calls
SUNRPC: Add API to force the client to disconnect
NFSv4/flexfiles: Cancel I/O if the layout is recalled or revoked
fs/nfs/flexfilelayout/flexfilelayout.c | 84 +++++++++++++++++++++++++-
fs/nfs/pnfs.c | 9 ++-
fs/nfs/pnfs.h | 9 +++
include/linux/sunrpc/clnt.h | 1 +
include/linux/sunrpc/sched.h | 6 ++
net/sunrpc/clnt.c | 57 +++++++++++++++--
net/sunrpc/sched.c | 51 +++++++++++-----
net/sunrpc/xprtsock.c | 3 +-
8 files changed, 194 insertions(+), 26 deletions(-)
--
2.37.3
next reply other threads:[~2022-10-05 20:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 19:57 trondmy [this message]
2022-10-05 19:57 ` [PATCH 1/4] SUNRPC: Fix races with rpc_killall_tasks() trondmy
2022-10-05 19:57 ` [PATCH 2/4] SUNRPC: Add a helper to allow pNFS drivers to selectively cancel RPC calls trondmy
2022-10-05 19:57 ` [PATCH 3/4] SUNRPC: Add API to force the client to disconnect trondmy
2022-10-05 19:57 ` [PATCH 4/4] NFSv4/flexfiles: Cancel I/O if the layout is recalled or revoked trondmy
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=20221005195738.4552-1-trondmy@kernel.org \
--to=trondmy@kernel.org \
--cc=anna.schumaker@netapp.com \
--cc=linux-nfs@vger.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;
as well as URLs for NNTP newsgroup(s).