From: cel@kernel.org
To: <linux-nfs@vger.kernel.org>
Cc: Olga Kornievskaia <kolga@netapp.com>,
Dai Ngo <dai.ngo@oracle.com>,
Chuck Lever <chuck.lever@oracle.com>
Subject: [RFC PATCH 0/6] Add a client-side OFFLOAD_STATUS implementation
Date: Tue, 2 Jul 2024 11:19:48 -0400 [thread overview]
Message-ID: <20240702151947.549814-8-cel@kernel.org> (raw)
From: Chuck Lever <chuck.lever@oracle.com>
*** COMPILE-TESTED ONLY ***
Not sure I've addressed all of Olga's concerns. This is more like a
progress report. I've more-or-less worked out how to sort through
the results of the operation and return a "bytes copied so far"
count to the caller.
Chuck Lever (6):
NFS: Fix typo in OFFLOAD_CANCEL comment
NFS: Implement NFSv4.2's OFFLOAD_STATUS XDR
NFS: Rename struct nfs4_offloadcancel_data
NFS: Implement NFSv4.2's OFFLOAD_STATUS operation
NFS: Use NFSv4.2's OFFLOAD_STATUS operation
NFS: Refactor trace_nfs4_offload_cancel
fs/nfs/nfs42proc.c | 173 ++++++++++++++++++++++++++++++++++----
fs/nfs/nfs42xdr.c | 88 ++++++++++++++++++-
fs/nfs/nfs4trace.h | 11 ++-
fs/nfs/nfs4xdr.c | 1 +
include/linux/nfs4.h | 1 +
include/linux/nfs_fs_sb.h | 1 +
include/linux/nfs_xdr.h | 5 +-
7 files changed, 260 insertions(+), 20 deletions(-)
--
2.45.2
next reply other threads:[~2024-07-02 15:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 15:19 cel [this message]
2024-07-02 15:19 ` [RFC PATCH 1/6] NFS: Fix typo in OFFLOAD_CANCEL comment cel
2024-07-02 15:19 ` [RFC PATCH 2/6] NFS: Implement NFSv4.2's OFFLOAD_STATUS XDR cel
2024-07-02 15:19 ` [RFC PATCH 3/6] NFS: Rename struct nfs4_offloadcancel_data cel
2024-07-02 15:19 ` [RFC PATCH 4/6] NFS: Implement NFSv4.2's OFFLOAD_STATUS operation cel
2024-07-02 18:30 ` Olga Kornievskaia
2024-07-02 18:33 ` Chuck Lever III
2024-07-02 15:19 ` [RFC PATCH 5/6] NFS: Use " cel
2024-07-02 18:30 ` Olga Kornievskaia
2024-07-02 18:43 ` Chuck Lever III
2024-07-03 18:52 ` Chuck Lever III
2024-07-02 15:19 ` [RFC PATCH 6/6] NFS: Refactor trace_nfs4_offload_cancel 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=20240702151947.549814-8-cel@kernel.org \
--to=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=kolga@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