All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wendy Cheng <wcheng@redhat.com>
To: Robert Rappaport <robert.rappaport@gmail.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: File system awareness (or lack thereof) of vfs granting of leases
Date: Sat, 17 Feb 2007 00:32:42 -0500	[thread overview]
Message-ID: <45D6937A.10902@redhat.com> (raw)
In-Reply-To: <f0a71180702161551p62a35dd7k27fefb4ab4092f81@mail.gmail.com>

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. IBM Research and University of Michigan CITI 
group have worked out a set of patches to remedy the issue:

http://www.opensubscriber.com/message/linux-fsdevel@vger.kernel.org/5527833.html

-- Wendy

  reply	other threads:[~2007-02-17  5:23 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 [this message]
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
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=45D6937A.10902@redhat.com \
    --to=wcheng@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=robert.rappaport@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.