From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever <cel@kernel.org>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2 0/4] Eliminate the RQ_SPLICE_OK flag
Date: Mon, 27 Nov 2023 15:21:57 -0500 [thread overview]
Message-ID: <2cbe4b0dec12498e1243ef86519e1cf4a69a8b6c.camel@kernel.org> (raw)
In-Reply-To: <170025895725.4577.18051288602708688381.stgit@bazille.1015granger.net>
On Fri, 2023-11-17 at 17:14 -0500, Chuck Lever wrote:
> The server's splice read path is used by the majority of exported
> filesystems. At last month's bake-a-thon, we tossed around some
> ideas about how to improve benchmarking and test coverage of the NFS
> server's vectored-read path, which is a fallback.
>
> One way to do this would be to expose a switch that can be set by
> test harnesses to disable splice reads.
>
> As an initial step, hoist RQ_SPLICE_OK out of the RPC layer. Later,
> I'll add a netlink command to as a switch between "use splice if
> possible" and "always use vectored reads". (I don't want to collide
> with the work Lorenzo is doing).
>
> Changes since v1:
> - Address "undefined reference to `svcauth_gss_flavor'"
>
> ---
>
> Chuck Lever (4):
> SUNRPC: Add a server-side API for retrieving an RPC's pseudoflavor
> NFSD: Replace RQ_SPLICE_OK in nfsd_read()
> NFSD: Modify NFSv4 to use nfsd_read_splice_ok()
> SUNRPC: Remove RQ_SPLICE_OK
>
>
> fs/nfsd/nfs4proc.c | 7 +++++--
> fs/nfsd/nfs4xdr.c | 13 ++++++++-----
> fs/nfsd/vfs.c | 26 +++++++++++++++++++++++++-
> fs/nfsd/vfs.h | 1 +
> fs/nfsd/xdr4.h | 1 +
> include/linux/sunrpc/svc.h | 2 --
> include/linux/sunrpc/svcauth.h | 7 ++++++-
> include/trace/events/sunrpc.h | 1 -
> net/sunrpc/auth_gss/svcauth_gss.c | 16 ++++++----------
> net/sunrpc/svc.c | 2 --
> net/sunrpc/svcauth.c | 16 ++++++++++++++++
> 11 files changed, 68 insertions(+), 24 deletions(-)
>
> --
> Chuck Lever
>
Reviewed-by: Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2023-11-27 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 22:14 [PATCH v2 0/4] Eliminate the RQ_SPLICE_OK flag Chuck Lever
2023-11-17 22:14 ` [PATCH v2 1/4] SUNRPC: Add a server-side API for retrieving an RPC's pseudoflavor Chuck Lever
2023-11-17 22:14 ` [PATCH v2 2/4] NFSD: Replace RQ_SPLICE_OK in nfsd_read() Chuck Lever
2023-11-17 22:14 ` [PATCH v2 3/4] NFSD: Modify NFSv4 to use nfsd_read_splice_ok() Chuck Lever
2023-11-17 22:14 ` [PATCH v2 4/4] SUNRPC: Remove RQ_SPLICE_OK Chuck Lever
2023-11-27 20:21 ` Jeff Layton [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=2cbe4b0dec12498e1243ef86519e1cf4a69a8b6c.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=cel@kernel.org \
--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