From: Steve French <smfrench@austin.rr.com>
To: Robert Love <rml@novell.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
linux-kernel@vger.kernel.org
Subject: Re: which ioctls matter across filesystems
Date: Fri, 29 Apr 2005 15:47:13 -0500 [thread overview]
Message-ID: <42729D51.5050203@austin.rr.com> (raw)
In-Reply-To: <1114805033.6682.150.camel@betsy>
Robert Love wrote:
>>What about inotify makes it insufficient for your needs?
>>
>>
>>
I am not sure - but it is obviously required that inotify can pass over
CIFS (and probably NFS) since change notification is hardest for the
user to figure out when they are on a network. I am not sure how the
filesystem can detect that a new watch is added to one of its inodes -
it looks like you added an ioctl to a device but I am still reading
through your latest patch. I was looking for something like an inode
operation that cifs could hook so the fs could be told when a new watch
was added or one was changed. In any case I need to construct
functions somewhat similar to what is in fs/cifs/fcntl.c and need to
finish/modify CIFSSMBNotify in fs/cifs/cifssmb.c to map the inotify
flags to the flags available in the CIFS network protocol specifications.
The existing network protocol support for ChangeNotify is more
straightforward than you might think and the filter flags & actions that
I have at my disposal for implementing notify across the network are in
fs/cifs/cifspdu.h already (search for FILE_ACTION_ and FILE_NOTIFY_ if
you are curious) but obviously they are similar to what the other Samba
team guys have already told you.
>>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)?
>>
>>
>
>A few worksets:
>
> - Current users, such as FAM and Samba, that need simple file
> change notification
> - Random applications that want to watch a file or two
> - The Linux desktop
> - Real-time live-updating indexing systems, such as Beagle,
> that compete with f.e. Apple's Spotlight.
>
>Best,
>
> Robert Love
>
strongly agree, very strongly agree.
The one example we left out - distributed backup applications (those
guys query me from time to time asking for improvements) - they want to
know when a server file changes so they can do backup across CIFS.
next prev parent reply other threads:[~2005-04-29 20:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-29 19:22 which ioctls matter across filesystems Steve French
2005-04-29 19:53 ` Trond Myklebust
2005-04-29 20:03 ` Robert Love
2005-04-29 20:42 ` Trond Myklebust
2005-04-29 20:47 ` Robert Love
2005-04-29 21:13 ` Trond Myklebust
2005-04-29 21:22 ` Steve French
2005-04-29 21:38 ` Trond Myklebust
2005-04-29 20:55 ` Steve French
2005-04-29 20:57 ` Robert Love
2005-04-29 21:05 ` Steve French
2005-04-29 20:47 ` Steve French [this message]
2005-04-29 20:50 ` Robert Love
2005-04-29 21:00 ` Steve French
2005-04-29 20:32 ` Steve French
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=42729D51.5050203@austin.rr.com \
--to=smfrench@austin.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@novell.com \
--cc=trond.myklebust@fys.uio.no \
/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