public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: cel@kernel.org
To: Trond Myklebust <trond.myklebust@hammerspace.com>,
	Anna Schumaker <anna@kernel.org>
Cc: <linux-nfs@vger.kernel.org>, Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH v4 0/7] Client-side OFFLOAD_STATUS implementation
Date: Fri, 31 Jan 2025 19:34:40 -0500	[thread overview]
Message-ID: <20250201003447.54614-1-cel@kernel.org> (raw)

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 an NFSv4.2 CB_OFFLOAD callback).

Therefore, a polling mechanism is needed. The NFSv4.2 protocol
provides one in the form of the its 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 v3:
- Change to fixed lease_time/2 timeout before posting OFFLOAD_STATUS
- Check if CB_OFFLOAD arrived if OFFLOAD_STATUS returned BAD_STATEID
- Added Olga's R-b and T-b tags

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        | 195 ++++++++++++++++++++++++++++++++++----
 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, 282 insertions(+), 25 deletions(-)

-- 
2.47.0


             reply	other threads:[~2025-02-01  0:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-01  0:34 cel [this message]
2025-02-01  0:34 ` [PATCH v4 1/7] NFS: CB_OFFLOAD can return NFS4ERR_DELAY cel
2025-02-01  0:34 ` [PATCH v4 2/7] NFS: Fix typo in OFFLOAD_CANCEL comment cel
2025-02-01  0:34 ` [PATCH v4 3/7] NFS: Rename struct nfs4_offloadcancel_data cel
2025-02-01  0:34 ` [PATCH v4 4/7] NFS: Implement NFSv4.2's OFFLOAD_STATUS XDR cel
2025-02-01  0:34 ` [PATCH v4 5/7] NFS: Implement NFSv4.2's OFFLOAD_STATUS operation cel
2025-02-01  0:34 ` [PATCH v4 6/7] NFS: Use " cel
2025-02-01  0:34 ` [PATCH v4 7/7] 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=20250201003447.54614-1-cel@kernel.org \
    --to=cel@kernel.org \
    --cc=anna@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --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