linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: linux-fsdevel@vger.kernel.org
Cc: nfs@lists.sourceforge.net, Marc Eshel <eshel@almaden.ibm.com>
Subject: Re: asynchronous locks for cluster exports
Date: Mon, 26 Feb 2007 14:52:32 -0500	[thread overview]
Message-ID: <20070226195232.GC6412@fieldses.org> (raw)

On Sat, Feb 03, 2007 at 12:30:55AM -0500, J. Bruce Fields wrote:
> 
> This is another attempt at a posix locking interface that allows us to
> provide NFS clients with cluster-coherent locking without blocking lockd
> while the filesystem goes off and talks to other nodes.

Marc and I have an updated version of this at:

	git://linux-nfs.org/~bfields/linux.git

(See the server-cluster-locking-api branch.)

Changes include:

	- bugfixes for GFS2; thanks to some setup help from Wendy Chang
	  and others, Marc has been able to run locking tests against an
	  nfs-exported GFS2 filesystem
	- preallocation of storage for conflicting lock in lockd's
	  testlock implementation, to avoid a race identified by Trond
	- Cleanup suggested by Christoph and others, including:
		- creation of posix-to-flock helper functions
		- rewrite of posix_test_lock interface to agree with
		  ->lock( ,F_GETLK, )
		- removal of some unnecessary parentheses, untangling of
		  some slightly tortured logic

We're hoping to get a detailed review from Trond sometime in the coming
month, after which we'll probably mailbomb linux-fsdevel again, but
any comments are welcome in the meantime.

--b.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2007-02-26 19:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-26 19:52 J. Bruce Fields [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-02-03  8:39 asynchronous locks for cluster exports Christoph Hellwig
2007-02-04  1:44 ` J. Bruce Fields
2007-02-03  5:30 J. Bruce Fields
2007-02-03  5:30 J. Bruce Fields
2006-12-06  5:34 J. Bruce Fields
2006-12-07 16:51 ` Christoph Hellwig
2006-12-14 22:51   ` J. Bruce Fields
2006-12-15 19:51 ` 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=20070226195232.GC6412@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=eshel@almaden.ibm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    /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).