From: "Robert Rappaport" <robert.rappaport@gmail.com>
To: "J. Bruce Fields" <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 10:46:51 -0500 [thread overview]
Message-ID: <f0a71180702200746k6da1db84sb6d8da19189e1dc0@mail.gmail.com> (raw)
In-Reply-To: <20070218063948.GC22022@fieldses.org>
On 2/18/07, J. Bruce Fields <bfields@fieldses.org> wrote:
> On Sat, Feb 17, 2007 at 12:32:42AM -0500, Wendy Cheng wrote:
> > Robert Rappaport wrote:
> >
> > >[snip]
> > >.... This is because the vfs running on the same node where the
> > >samba server is running is not necessarily aware of all accesses to
> > >the file on which it is granting a lease. Since vfs does not
> > >currently inform file systems about the granting and rescinding of
> > >leases, a clustered file system cannot allow a samba server to support
> > >OpLocks on its files and this has a negative impact on performance.
> > >
> > >What I think is needed is to add a file systems defined
> > >file_operations function, that would be invoked when vfs is
> > >considering the granting of a lease on a file associated with an
> > >inode. Such an enhancement would allow a file system to be come aware
> > >of vfs lease activity and allow it to support this activity.
> > >
> > NFS has similar issues because Linux NLM-VFS does not invoke server side
> > filesystem specific lock method. This implies NFS client applications is
> > not able to use posix locks to coordinate file access across different
> > nodes with a cluster filesystem, even the cluster filesystem itself
> > does support posix locking.
>
> We also have the same problem with leases, since we're using leases to
> implement NFSv4 delegations. There's a simple-minded patch here:
>
> http://linux-nfs.org/cgi-bin/gitweb.cgi?p=bfields-2.6.git;a=commitdiff;h=4e8aff5dabe07b2e4e95ef0c741a34f65409087f
>
> I'm not really sure if it's right.
>
> --b.
>
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.
- Robert Rappaport
next prev parent reply other threads:[~2007-02-20 15:46 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 [this message]
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
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=f0a71180702200746k6da1db84sb6d8da19189e1dc0@mail.gmail.com \
--to=robert.rappaport@gmail.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).