From: Greg Banks <gnb@sgi.com>
To: "Ara.T.Howard" <Ara.T.Howard@noaa.gov>
Cc: 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 09:54:11 +1100 [thread overview]
Message-ID: <20041108225411.GA29190@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0411081021570.16292@harp.ngdc.noaa.gov>
On Mon, Nov 08, 2004 at 10:27:19AM -0700, Ara.T.Howard wrote:
> On Tue, 26 Oct 2004, Greg Banks wrote:
> if i read your code right it looks like, once max delay is reached, it stays
> there.
Yes.
> this will mean that a client waiting a long time has an increasingly
> significant change of being starved when a lock is under heavy contention
> doesn't it?
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.
> in any case it seems like resetting the delay to min after
> reaching max (becoming impatient again) may give better performance on
> average
> than simply staying at max.
Could do. Do you want to do the patch?
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-11-08 22:59 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 [this message]
2004-11-08 23:17 ` Ara.T.Howard
2004-11-09 9:17 ` Olaf Kirch
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=20041108225411.GA29190@sgi.com \
--to=gnb@sgi.com \
--cc=Ara.T.Howard@noaa.gov \
--cc=gnb@melbourne.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