From: Bruce Fields <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: still seeing single client NFS4ERR_DELAY / CB_RECALL
Date: Mon, 10 Aug 2020 16:10:01 -0400 [thread overview]
Message-ID: <20200810201001.GC13266@fieldses.org> (raw)
In-Reply-To: <00CAA5B7-418E-4AB5-AE08-FE2F87B06795@oracle.com>
On Mon, Aug 10, 2020 at 04:01:00PM -0400, Chuck Lever wrote:
> Roughly the same result with this patch as with the first one. The
> first one is a little better. Plus, I think the Solaris NFS server
> hands out write delegations on v4.0, and I haven't heard of a
> significant issue there. It's heuristics may be different, though.
>
> So, it might be that NFSv4.0 has always run significantly slower. I
> will have to try a v5.4 or older server to see.
Oh, OK, I was assuming this was a regression.
> Also, instead of timing, I should count forward channel RPCs and
> callbacks, or perhaps the number of DELAY responses.
Thanks for looking into this!
--b.
next prev parent reply other threads:[~2020-08-10 20:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-09 17:11 still seeing single client NFS4ERR_DELAY / CB_RECALL Chuck Lever
2020-08-09 20:27 ` Bruce Fields
2020-08-09 21:25 ` Bruce Fields
2020-08-10 18:21 ` Chuck Lever
2020-08-10 19:07 ` Bruce Fields
2020-08-10 20:01 ` Chuck Lever
2020-08-10 20:10 ` Bruce Fields [this message]
2020-08-11 13:31 ` Chuck Lever
2020-08-16 20:46 ` Chuck Lever
2020-08-17 22:20 ` Bruce Fields
2020-08-18 15:27 ` Chuck Lever
2020-08-18 21:26 ` Chuck Lever
2020-08-18 21:49 ` Bruce Fields
2020-08-19 13:26 ` Chuck Lever
2020-08-19 21:29 ` Bruce Fields
2020-08-20 12:56 ` Chuck Lever
2020-08-24 13:39 ` Chuck Lever
2020-08-24 14:22 ` Bruce Fields
2020-08-24 15:42 ` Chuck Lever
2020-09-04 22:01 ` Bruce Fields
2020-09-04 22:27 ` Chuck Lever
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=20200810201001.GC13266@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.