From: Chuck Lever <cel@kernel.org>
To: NeilBrown <neil@brown.name>, Jeff Layton <jlayton@kernel.org>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: <linux-nfs@vger.kernel.org>, Chuck Lever <chuck.lever@oracle.com>
Subject: [RFC PATCH 0/3] Remove the max-ops-per-compound-limit
Date: Tue, 10 Jun 2025 12:05:06 -0400 [thread overview]
Message-ID: <20250610160509.97599-1-cel@kernel.org> (raw)
From: Chuck Lever <chuck.lever@oracle.com>
After some discussion last year, Jeff reasoned that there was no
architectural reason NFSD has to restrict the number of
operations per NFSv4 COMPOUND. This is an experimental series to
explore that idea.
Chuck Lever (3):
NFSD: Rename a function parameter
NFSD: Make nfsd_genl_rqstp::rq_ops array best-effort
NFSD: Remove the cap on number of operations per NFSv4 COMPOUND
fs/nfsd/nfs4proc.c | 14 ++------------
fs/nfsd/nfs4state.c | 1 -
fs/nfsd/nfs4xdr.c | 4 +---
fs/nfsd/nfsctl.c | 31 ++++++++++++++++---------------
fs/nfsd/nfsd.h | 5 +----
fs/nfsd/xdr4.h | 1 -
6 files changed, 20 insertions(+), 36 deletions(-)
--
2.49.0
next reply other threads:[~2025-06-10 16:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 16:05 Chuck Lever [this message]
2025-06-10 16:05 ` [RFC PATCH 1/3] NFSD: Rename a function parameter Chuck Lever
2025-06-10 16:05 ` [RFC PATCH 2/3] NFSD: Make nfsd_genl_rqstp::rq_ops array best-effort Chuck Lever
2025-06-10 16:05 ` [RFC PATCH 3/3] NFSD: Remove the cap on number of operations per NFSv4 COMPOUND Chuck Lever
2025-06-10 17:01 ` Jeff Layton
2025-06-10 17:07 ` Chuck Lever
2025-06-10 17:28 ` [RFC PATCH 0/3] Remove the max-ops-per-compound-limit Jeff Layton
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=20250610160509.97599-1-cel@kernel.org \
--to=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=tom@talpey.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.