From: David Teigland <teigland@redhat.com>
To: Robert Rappaport <robert.rappaport@gmail.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
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 13:08:17 -0600 [thread overview]
Message-ID: <20070220190817.GB3932@redhat.com> (raw)
In-Reply-To: <f0a71180702200746k6da1db84sb6d8da19189e1dc0@mail.gmail.com>
On Tue, Feb 20, 2007 at 10:46:51AM -0500, Robert Rappaport wrote:
> Thank you both for your helpful replies. In particular, the addition
> of the calls to file system specific functions in routines,
> fcntl_setlease() and break_lease(), as well as the modifications to
> the file_operations and inode_operations structures, pointed to by
> Bruce's reply, look exactly like the hooks that I would need to
> proceed to resolve my problems. Is there any timetable established
> for these modifications to make it into a future release? These hooks
> would clearly benefit any cluster file system that has to deal with
> leases.
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.
Dave
next prev parent reply other threads:[~2007-02-20 19:07 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 [this message]
2007-02-20 20:51 ` bfields
2007-02-20 20:55 ` bfields
2007-02-20 21:25 ` David Teigland
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=20070220190817.GB3932@redhat.com \
--to=teigland@redhat.com \
--cc=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=robert.rappaport@gmail.com \
--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).