On Sat, 2025-03-01 at 13:31 -0500, cel@xxxxxxxxxx wrote:
> From: Chuck Lever <chuck.lever@xxxxxxxxxx>
>
> Try not to prolong the wait for completion of a COPY or COPY_NOTIFY
> operation.
>
> Signed-off-by: Chuck Lever <chuck.lever@xxxxxxxxxx>
> ---
> fs/nfsd/nfs4proc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/nfsd/nfs4proc.c b/fs/nfsd/nfs4proc.c
> index 9a0e68aa246f..3431b695882d 100644
> --- a/fs/nfsd/nfs4proc.c
> +++ b/fs/nfsd/nfs4proc.c
> @@ -1712,7 +1712,7 @@ static int nfsd4_cb_offload_done(struct nfsd4_callback *cb,
> switch (task->tk_status) {
> case -NFS4ERR_DELAY:
> if (cbo->co_retries--) {
> - rpc_delay(task, 1 * HZ);
> + rpc_delay(task, HZ / 5);
> return 0;
> }
> }
This is fine for now.
What I think we probably ought to do for all the callbacks is implement
a sliding delay window, and handle it in the common rpc_call_done
handling code.
--
Jeff Layton <jlayton@xxxxxxxxxx>
