From: "J. Bruce Fields" <bfields@fieldses.org>
To: Frank Steiner <fsteiner-mail1@bio.ifi.lmu.de>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Parallel file locking quite slow with vers=4.0 compared to vers=3
Date: Tue, 21 Jul 2015 11:51:44 -0400 [thread overview]
Message-ID: <20150721155144.GC11050@fieldses.org> (raw)
In-Reply-To: <55ADEA5C.8020607@bio.ifi.lmu.de>
On Tue, Jul 21, 2015 at 08:44:44AM +0200, Frank Steiner wrote:
> J. Bruce Fields wrote
>
> > One way to confirm that might be to run client kernels modified to make
> > the polling behavior (controlled by
> > fs/nfs/nfs4proc.c:nfs4_set_lock_task_retry()) more aggressive, and see
> > if that removes the delays in your case.
> >
> > If that works, then it might also be worth considering implementing
> > CB_NOTIFY_LOCK:
> >
> > https://tools.ietf.org/html/rfc5661#page-593
>
> I wouldn't mind to test any kind of patch if someone would find the time
> to provide some. Writing them myself is beyond my skills I'm afraid :-)
Well, I was just thinking of something like this.
(*Not* saying this is what we really want to do, but it might help
confirm where your delay is coming from.)
--b.
diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
index 6f228b5..c119ba7 100644
--- a/fs/nfs/nfs4proc.c
+++ b/fs/nfs/nfs4proc.c
@@ -5367,7 +5367,7 @@ int nfs4_proc_delegreturn(struct inode *inode, struct rpc_cred *cred, const nfs4
return err;
}
-#define NFS4_LOCK_MINTIMEOUT (1 * HZ)
+#define NFS4_LOCK_MINTIMEOUT (1 * HZ / 10)
#define NFS4_LOCK_MAXTIMEOUT (30 * HZ)
/*
next prev parent reply other threads:[~2015-07-21 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 14:02 Parallel file locking quite slow with vers=4.0 compared to vers=3 Frank Steiner
2015-07-20 21:23 ` J. Bruce Fields
2015-07-21 6:44 ` Frank Steiner
2015-07-21 15:51 ` J. Bruce Fields [this message]
2015-07-22 14:49 ` Frank Steiner
2015-07-22 14:53 ` Frank Steiner
2015-07-22 15:40 ` 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=20150721155144.GC11050@fieldses.org \
--to=bfields@fieldses.org \
--cc=fsteiner-mail1@bio.ifi.lmu.de \
--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