linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] AFS: Implement file locking
Date: Sun, 27 May 2007 09:51:10 +0100	[thread overview]
Message-ID: <18750.1180255870@redhat.com> (raw)
In-Reply-To: <20070527022502.GB10867@fieldses.org>

J. Bruce Fields <bfields@fieldses.org> wrote:

> > > Do you allow upgrades and downgrades?  (Just curious.)
> > 
> > AFS does not, as far as I know.
> 
> So if I request a write lock while holding a read lock, my request will
> be denied?

At the moment, yes.  Don't the POSIX and flock lock-handling routines in the
kernel normally do that anyway?

> This is a little strange, though--if there's somebody waiting for a
> write lock on an inode (because somebody else already holds a read lock
> on it), that shouldn't block requests for read locks.

That depends on whether you want fairness or not.  Allowing read locks to jump
the queue like this can lead to starvation for your writers.

David

  parent reply	other threads:[~2007-05-27  8:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-24 16:55 [PATCH] AFS: Implement file locking David Howells
2007-05-25  7:31 ` Jiri Slaby
2007-05-26  2:23 ` J. Bruce Fields
2007-05-26  3:11   ` Kyle Moffett
2007-05-27  0:12   ` David Howells
2007-05-26 23:55 ` David Howells
2007-05-27  2:25   ` J. Bruce Fields
2007-05-27  8:51   ` David Howells [this message]
2007-05-27 16:12     ` J. Bruce Fields
2007-05-29  9:34     ` David Howells
2007-05-29 20:08       ` J. Bruce Fields
2007-05-29 12:43     ` David Howells

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=18750.1180255870@redhat.com \
    --to=dhowells@redhat.com \
    --cc=akpm@osdl.org \
    --cc=bfields@fieldses.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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).