From: Mikael Davranche <mikael.davranche@free.fr>
To: Trond Myklebust <Trond.Myklebust@netapp.com>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: [PATCH 0/3] NLM: Proposal for a timeout setting on blocking locks
Date: Tue, 11 Mar 2008 13:14:25 +0100 [thread overview]
Message-ID: <1205237665.47d677a143941@imp.free.fr> (raw)
Hi,
When a lock blocks, the server sends us a BLOCKED message. When it releases, it
may sends us an NLM callback. When it does not (it depends on NLM
implementations), the client waits for 30 seconds before attempting to reclaim
the lock again.
The 30 seconds time is hard-coded on fs/lockd/clntproc.c:
#define NLMCLNT_POLL_TIMEOUT (30*HZ)
30 seconds is generally suitable, but in some cases, it is too much and it may
be set to less than that. I have this problem in my production env
ironment when an e-mail box receives more than 1 e-mail every 30 seconds. In
that particular case, the nlm_blocked list grows up and never reduce
s. Setting this time to less than 30 seconds resolves the problem.
This short series of patches enables the set of this timeout, setting a new
/proc entry named nlm_clnt_poll_timeout (this name is based on the NL
MCLNT_POLL_TIMEOUT define). Patches are based on the 2.6.24.3 version (is that a
problem? may I base them on the 2.6.25-rc5 one?).
What do you think about this? Any comments are very welcome.
Cheers, Mikael
--
Mikael Davranche
System Engineer
Atos Worldline, France
next reply other threads:[~2008-03-11 12:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 12:14 Mikael Davranche [this message]
2008-03-11 12:15 ` [PATCH 1/3] NLM: Proposal for a timeout setting on blocking locks Mikael Davranche
2008-03-11 12:16 ` [PATCH 2/3] " Mikael Davranche
2008-03-11 12:18 ` [PATCH 3/3] " Mikael Davranche
2008-03-11 23:25 ` [PATCH 0/3] " Trond Myklebust
2008-03-12 11:26 ` Mikael Davranche
2008-03-12 13:33 ` Trond Myklebust
2008-03-12 15:51 ` Mikael Davranche
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=1205237665.47d677a143941@imp.free.fr \
--to=mikael.davranche@free.fr \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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).