From: "J. Bruce Fields" <bfields@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Jeff Layton <jlayton@redhat.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: nfsd: delegation conflicts between NFSv3 and NFSv4 accessors
Date: Mon, 13 Mar 2017 12:06:32 -0400 [thread overview]
Message-ID: <20170313160631.GE11746@parsley.fieldses.org> (raw)
In-Reply-To: <20170313160145.GD11746@parsley.fieldses.org>
On Mon, Mar 13, 2017 at 12:01:45PM -0400, J. Bruce Fields wrote:
> That wait doesn't sound bad at all.
>
> The server could track round trip times to the clients holding
> delegations and use that to estimate the right wait time, but hopefully
> that's overkill.
>
> I think the occasional retransmitted truncate probably isn't a big deal.
> Seems like the kind of thing the reply cache would handle well.
I haven't thought about what it'd take to implement. Just for testing
purposes, maybe stick a 50ms wait and a retry in the JUKEBOX case in
anything under fs/nfsd/nfs3proc.c that looks like it could break a
delegation.
Jeff's proposal should also be pretty easy to prototype.
--b.
next prev parent reply other threads:[~2017-03-13 16:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-11 16:53 nfsd: delegation conflicts between NFSv3 and NFSv4 accessors Chuck Lever
2017-03-11 17:08 ` Jeff Layton
2017-03-11 20:46 ` Chuck Lever
2017-03-11 21:04 ` Jeff Layton
2017-03-13 13:27 ` J. Bruce Fields
2017-03-13 15:30 ` Chuck Lever
2017-03-13 16:01 ` J. Bruce Fields
2017-03-13 16:06 ` J. Bruce Fields [this message]
2017-03-13 16:33 ` Jeff Layton
2017-03-13 17:12 ` Chuck Lever
2017-03-13 18:26 ` Chuck Lever
2017-03-14 14:05 ` Jeff Layton
2017-03-14 13:55 ` J. Bruce Fields
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=20170313160631.GE11746@parsley.fieldses.org \
--to=bfields@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).