From: cel@kernel.org
To: Neil Brown <neilb@suse.de>, 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] Implement referring call lists for CB_OFFLOAD
Date: Fri, 14 Feb 2025 10:57:43 -0500 [thread overview]
Message-ID: <20250214155746.18016-1-cel@kernel.org> (raw)
From: Chuck Lever <chuck.lever@oracle.com>
I've built a naive proof-of-concept of the csa_referring_call_list
argument of the CB_SEQUENCE operation, and hooked it up for the
CB_OFFLOAD callback operation.
This has been pushed to my kernel.org "fix-async-copy" branch for
folks to play around with.
Compile-tested only. I'm sure this is still full of bugs and
misunderstanding.
Chuck Lever (3):
NFSD: Record call's slot index
NFSD: Implement CB_SEQUENCE referring call lists
NFSD: Use a referring call list for CB_OFFLOAD
fs/nfsd/nfs4callback.c | 132 +++++++++++++++++++++++++++++++++++++++--
fs/nfsd/nfs4proc.c | 10 ++++
fs/nfsd/nfs4state.c | 1 +
fs/nfsd/state.h | 22 +++++++
fs/nfsd/xdr4.h | 5 ++
fs/nfsd/xdr4cb.h | 5 +-
6 files changed, 169 insertions(+), 6 deletions(-)
--
2.47.0
next reply other threads:[~2025-02-14 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 15:57 cel [this message]
2025-02-14 15:57 ` [RFC PATCH 1/3] NFSD: Record call's slot index cel
2025-02-14 18:26 ` Jeff Layton
2025-02-14 15:57 ` [RFC PATCH 2/3] NFSD: Implement CB_SEQUENCE referring call lists cel
2025-02-14 15:57 ` [RFC PATCH 3/3] NFSD: Use a referring call list for CB_OFFLOAD cel
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=20250214155746.18016-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=neilb@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox