From: Olaf Kirch <okir@suse.de>
To: Greg Banks <gnb@sgi.com>
Cc: "Ara.T.Howard" <Ara.T.Howard@noaa.gov>,
Greg Banks <gnb@melbourne.sgi.com>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
Linux NFS Mailing List <nfs@lists.sourceforge.net>
Subject: Re: [PATCH] exponential backoff for blocked LOCK call polling
Date: Tue, 9 Nov 2004 10:17:04 +0100 [thread overview]
Message-ID: <20041109091704.GA14350@suse.de> (raw)
In-Reply-To: <20041108225411.GA29190@sgi.com>
On Tue, Nov 09, 2004 at 09:54:11AM +1100, Greg Banks wrote:
> Not if the server has queued the lock request. But then if the server
> were correctly implemented it would probably be sending us a GRANTED
> callback and we wouldn't need to poll.
The Linux lockd should send a GRANTED message. The only reason I
implemented polling was as a workaround against broken lockd's that would
never send GRANTED messages if you used the (synchronous) NLM_LOCK call
instead of the (asynchronous) NLM_LOCK_MSG. HPUX 10.something was one
of them.
I agree though that the polling code is bad because it masks potential
bugs in the Linux lockd.
Olaf
--
Olaf Kirch | Things that make Monday morning interesting, #1:
okir@suse.de | "I want to use NFS over AX25, can you help me?"
---------------+
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2004-11-09 9:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 10:22 [PATCH] exponential backoff for blocked LOCK call polling Greg Banks
2004-11-08 17:27 ` Ara.T.Howard
2004-11-08 22:54 ` Greg Banks
2004-11-08 23:17 ` Ara.T.Howard
2004-11-09 9:17 ` Olaf Kirch [this message]
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=20041109091704.GA14350@suse.de \
--to=okir@suse.de \
--cc=Ara.T.Howard@noaa.gov \
--cc=gnb@melbourne.sgi.com \
--cc=gnb@sgi.com \
--cc=nfs@lists.sourceforge.net \
--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