linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-fsdevel@vger.kernel.org, nfs@lists.sourceforge.net,
	Marc Eshel <eshel@almaden.ibm.com>
Subject: Re: asynchronous locks for cluster exports
Date: Sat, 3 Feb 2007 20:44:58 -0500	[thread overview]
Message-ID: <20070204014458.GF7588@fieldses.org> (raw)
In-Reply-To: <20070203083929.GA18828@infradead.org>

On Sat, Feb 03, 2007 at 08:39:29AM +0000, Christoph Hellwig wrote:
> On Sat, Feb 03, 2007 at 12:30:55AM -0500, J. Bruce Fields wrote:
> > The gfs2 implementation in the last patch is (unfortunately) still just
> > a rough draft that needs some more thought and some testing.
> 
> So what exactly in this patch is tested?

Marc's testing this stuff against gpfs.  Yeah, I know, I know.  I'm not
asking this be merged until it makes sense purely from the point of view
of in-tree users.

Right now all we know is that it doesn't appear to break local or NFS
locking, that it works for one out-of-tree filesystem, and that it looks
like it should be right for gfs--but the gfs implementation is just a
sketch, totally untested.  I'm here at connectathon working with one of
the gfs developers, so hopefully that should change soon.

We'd like to work with ocfs too at some point, but last I heard they
hadn't yet tried to implement cluster-coherent posix locking.

--b.

  reply	other threads:[~2007-02-04  1:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-03  8:39 asynchronous locks for cluster exports Christoph Hellwig
2007-02-04  1:44 ` J. Bruce Fields [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-02-26 19:52 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=20070204014458.GF7588@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=eshel@almaden.ibm.com \
    --cc=hch@infradead.org \
    --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).