From: David Teigland <teigland@redhat.com>
To: bfields@fieldses.org
Cc: Wendy Cheng <wcheng@redhat.com>, linux-fsdevel@vger.kernel.org
Subject: Re: File system awareness (or lack thereof) of vfs granting of leases
Date: Tue, 20 Feb 2007 15:25:08 -0600 [thread overview]
Message-ID: <20070220212508.GD3932@redhat.com> (raw)
In-Reply-To: <38020.141.211.133.169.1172004714.squirrel@www.fieldses.org>
On Tue, Feb 20, 2007 at 03:51:54PM -0500, bfields@fieldses.org wrote:
> > On Tue, Feb 20, 2007 at 10:46:51AM -0500, Robert Rappaport wrote:
> > We did an experimental distributed lease implementation in gfs(1) a while
> > ago. It worked, but was so extremely expensive that there was no point in
> > considering it seriously. The problem is that _every_ open and close of
> > every file requires a new dlm lock operation. Leases require knowledge
> > about the cluster-wide opened/closed state of files, not only that but the
> > mode they're open in.
>
> We're using leases to implement NFSv4 delegations. Delegations are
> similar to leases--they come in read and write variants, and they give
> clients a guarantee that they'll be warned before another client is
> allowed to do a conflicting open--but delegations are completely optional.
> A server can deny a delegation for any reason, even when there isn't
> necessarily a conflicting open.
>
> So perhaps we need some way for nfsd to ask the filesystem to give it a
> lease, but only if it's easy to do so. Would it be possible to make it
> cheap for GFS to give out leases in some particular (hopefully common)
> cases?
I don't know of any shortcuts off hand, but there could certainly be some.
Doing something completely different and not using cluster locks may also
be worth investigating.
Dave
next prev parent reply other threads:[~2007-02-20 21:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 23:51 File system awareness (or lack thereof) of vfs granting of leases Robert Rappaport
2007-02-17 5:32 ` Wendy Cheng
2007-02-18 6:39 ` J. Bruce Fields
2007-02-20 15:46 ` Robert Rappaport
2007-02-20 16:33 ` J. Bruce Fields
2007-02-20 19:08 ` Robert Rappaport
2007-02-20 21:14 ` bfields
2007-02-20 21:57 ` Robert Rappaport
2007-02-20 19:08 ` David Teigland
2007-02-20 20:51 ` bfields
2007-02-20 20:55 ` bfields
2007-02-20 21:25 ` David Teigland [this message]
2007-02-22 21:58 ` J. Bruce Fields
2007-02-22 22:57 ` David Teigland
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=20070220212508.GD3932@redhat.com \
--to=teigland@redhat.com \
--cc=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=wcheng@redhat.com \
/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).