From: Jeff Layton <jlayton@kernel.org>
To: cel@kernel.org, Olga Kornievskaia <okorniev@redhat.com>,
Trond Myklebust <trond.myklebust@hammerspace.com>,
Anna Schumaker <anna@kernel.org>
Cc: linux-nfs@vger.kernel.org, Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [PATCH v2 0/7] Client-side OFFLOAD_STATUS implementation
Date: Fri, 20 Dec 2024 11:46:40 -0500 [thread overview]
Message-ID: <08370e59af140bef8a8cd8c0c7ea3139a4d03e52.camel@kernel.org> (raw)
In-Reply-To: <20241220154227.16873-9-cel@kernel.org>
On Fri, 2024-12-20 at 10:42 -0500, cel@kernel.org wrote:
> From: Chuck Lever <chuck.lever@oracle.com>
>
> SCSI implementation experience has shown that an interrupt-only
> COPY offload implementation is not reliable. There are too many
> common scenarios where the client can miss the completion interrupt
> (in our case, this is a CB_OFFLOAD callback).
>
> Therefore, a polling mechanism is needed. The NFSv4.2 protocol
> provides one in the form of the new OFFLOAD_STATUS operation. Linux
> NFSD implements OFFLOAD_STATUS already. This series adds a Linux NFS
> client implementation of the OFFLOAD_STATUS operation that can query
> the state of a background COPY on the server.
>
> These patches are also available here:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git/log/?h=fix-async-copy
>
> Changes since v1:
> - nfs42_proc_offload_status() now uses a synchronous RPC
>
> Chuck Lever (7):
> NFS: CB_OFFLOAD can return NFS4ERR_DELAY
> NFS: Fix typo in OFFLOAD_CANCEL comment
> NFS: Rename struct nfs4_offloadcancel_data
> NFS: Implement NFSv4.2's OFFLOAD_STATUS XDR
> NFS: Implement NFSv4.2's OFFLOAD_STATUS operation
> NFS: Use NFSv4.2's OFFLOAD_STATUS operation
> NFS: Refactor trace_nfs4_offload_cancel
>
> fs/nfs/callback_proc.c | 2 +-
> fs/nfs/nfs42proc.c | 188 ++++++++++++++++++++++++++++++++++----
> fs/nfs/nfs42xdr.c | 88 +++++++++++++++++-
> fs/nfs/nfs4proc.c | 3 +-
> 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 +-
> 9 files changed, 275 insertions(+), 25 deletions(-)
>
Nice work, Chuck. This all looks good to me.
Reviewed-by: Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2024-12-20 16:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 15:42 [PATCH v2 0/7] Client-side OFFLOAD_STATUS implementation cel
2024-12-20 15:42 ` [PATCH v2 1/7] NFS: CB_OFFLOAD can return NFS4ERR_DELAY cel
2024-12-20 15:42 ` [PATCH v2 2/7] NFS: Fix typo in OFFLOAD_CANCEL comment cel
2024-12-20 15:42 ` [PATCH v2 3/7] NFS: Rename struct nfs4_offloadcancel_data cel
2024-12-20 15:42 ` [PATCH v2 4/7] NFS: Implement NFSv4.2's OFFLOAD_STATUS XDR cel
2024-12-20 15:42 ` [PATCH v2 5/7] NFS: Implement NFSv4.2's OFFLOAD_STATUS operation cel
2024-12-20 15:42 ` [PATCH v2 6/7] NFS: Use " cel
2024-12-21 14:36 ` Olga Kornievskaia
2024-12-21 16:10 ` Chuck Lever
2024-12-20 15:42 ` [PATCH v2 7/7] NFS: Refactor trace_nfs4_offload_cancel cel
2024-12-20 16:46 ` 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=08370e59af140bef8a8cd8c0c7ea3139a4d03e52.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=anna@kernel.org \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=okorniev@redhat.com \
--cc=trond.myklebust@hammerspace.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