Re: which ioctls matter across filesystems

[Trond Myklebust <trond.myklebust@fys.uio.no>]

fr den 29.04.2005 Klokka 14:22 (-0500) skreiv Steve French:

> The new inotify mechanism being prototyped in -mm currently is the other 
> one which needs work to determine how to map it across the network.   
> Since it was added for support of Samba, the corresponding client part 
> (for cifs) may turn out to map to the network protocol quite well 
> already, and given NFSv4 having various similarities to CIFS, it would 
> be interesting if the semantics of inotify would map to NFSv4 write 
> protocol.

We are discussing the equivalent of dnotify as a potential candidate for
the first minor version of NFSv4, but not inotify.
The purpose of our dnotify implementation is address the needs of things
like file browsers that don't really care about synchronous notification
of changes, but that do currently cause a lot of unnecessary traffic on
the wire due to constantly polling stat() and doing readdir() updates.
The jury is still out as to whether or not the callbacks actually do
reduce on-the-wire traffic, though, so we may drop it.

What kind of real-world applications exist out there that need inotify
functionality, and what sort of requirements do they have (in particular
w.r.t. the notification mechanism)?

Cheers,
  Trond
-- 
Trond Myklebust <trond.myklebust@fys.uio.no>