fam
[Top] [All Lists]

[fam] Re: [prepatch] Directory Notification

To: "Theodore Y. Ts'o" <tytso@xxxxxxx>
Subject: [fam] Re: [prepatch] Directory Notification
From: Michael Gerdts <gerdts@xxxxxxxxxxxx>
Date: Mon, 22 May 2000 13:26:32 -0500
Cc: willy@xxxxxxxxxxxxxxxxxx, Erez Zadok <ezk@xxxxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxxx, tridge@xxxxxxxxxxxxx, fam@xxxxxxxxxxx
In-reply-to: <200005221225.IAA05370@xxxxxxxxxxxxxxxxx>; from tytso@xxxxxxx on Mon, May 22, 2000 at 08:25:05AM -0400
References: <20000521121830.X28590@xxxxxxxxxxxxxxxxxx> <200005221225.IAA05370@xxxxxxxxxxxxxxxxx>
Sender: owner-fam@xxxxxxxxxxx
On Mon, May 22, 2000 at 08:25:05AM -0400, Theodore Y. Ts'o wrote:
> A much more obvious place where directory notification won't work is for
> any kind of shared filesystem --- i.e., GFS, or any other networked
> filesystem (NFS, smbfs, etc.).  But that's for pretty obvious
> reasons....

My first thought was along these lines as well.  Sun faced a similar
situation with POSIX ACL's over NFS.  The solution was to make it so that
their nfsd added an nfs_acl service, which made commands like getfacl() and
setfacl() work properly over NFS.

It seems to me that directory notifications could be handled in a similar
manner without a whole lot of difficulty.  Applications (like always) would
just need to be aware that not all file systems will support this feature.
Additionall, the NFS client code would need to be aware that the server may
not support directory notifications.

Come to think of it, this could make it so that when both the NFS client
and the NFS server support directory notifications, the NFS client could
use this method to enhance the functionality of attribute caching.  Then
again, I have worked on all of about 3 lines of the NFS code.

Mike

--
Source code, list archive, and docs: http://oss.sgi.com/projects/fam/
To unsubscribe: echo unsubscribe fam | mail majordomo@xxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>