From: Jon Hunter <jonathanh@nvidia.com>
To: Trond Myklebust <trondmy@gmail.com>
Cc: <linux-nfs@vger.kernel.org>, linux-tegra <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH] SUNRPC: Avoid RPC delays when exiting suspend
Date: Wed, 6 Nov 2019 11:15:01 +0000 [thread overview]
Message-ID: <3f536791-dbd1-cc9a-c88a-ddc26dd57c00@nvidia.com> (raw)
In-Reply-To: <20191105142133.28741-1-trond.myklebust@hammerspace.com>
On 05/11/2019 14:21, Trond Myklebust wrote:
> Jon Hunter: "I have been tracking down another suspend/NFS related
> issue where again I am seeing random delays exiting suspend. The delays
> can be up to a couple minutes in the worst case and this is causing a
> suspend test we have to fail."
>
> Change the use of a deferrable work to a standard delayed one.
>
> Reported-by: Jon Hunter <jonathanh@nvidia.com>
> Fixes: 7e0a0e38fcfea ("SUNRPC: Replace the queue timer with a delayed work function")
> Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
> ---
> net/sunrpc/sched.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/sunrpc/sched.c b/net/sunrpc/sched.c
> index 360afe153193..987c4b1f0b17 100644
> --- a/net/sunrpc/sched.c
> +++ b/net/sunrpc/sched.c
> @@ -260,7 +260,7 @@ static void __rpc_init_priority_wait_queue(struct rpc_wait_queue *queue, const c
> rpc_reset_waitqueue_priority(queue);
> queue->qlen = 0;
> queue->timer_list.expires = 0;
> - INIT_DEFERRABLE_WORK(&queue->timer_list.dwork, __rpc_queue_timer_fn);
> + INIT_DELAYED_WORK(&queue->timer_list.dwork, __rpc_queue_timer_fn);
> INIT_LIST_HEAD(&queue->timer_list.list);
> rpc_assign_waitqueue_name(queue, qname);
> }
Thanks!
Tested-by: Jon Hunter <jonathanh@nvidia.com>
Cheers
Jon
--
nvpublic
next prev parent reply other threads:[~2019-11-06 11:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <329228f8-e194-a021-9226-69a9b6a403ce@nvidia.com>
2019-11-05 14:21 ` [PATCH] SUNRPC: Avoid RPC delays when exiting suspend Trond Myklebust
2019-11-06 11:15 ` Jon Hunter [this message]
2019-11-18 10:21 ` Jon Hunter
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=3f536791-dbd1-cc9a-c88a-ddc26dd57c00@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=trondmy@gmail.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