From: Javier Fernandez-Ivern <ivern@acm.org>
To: rudi@lambda-computing.de
Cc: viro@math.psu.edu, linux-kernel@vger.kernel.org
Subject: Re: File change notification
Date: Wed, 31 Dec 2003 10:20:22 -0800 [thread overview]
Message-ID: <3FF31366.30206@acm.org> (raw)
In-Reply-To: <3FF2FC85.5070906@lambda-computing.de>
Rüdiger Klaehn wrote:
> I have been wondering for some time why there is no decent file change
> notification mechanism in linux. Is there some deep philosophical reason
> for this, or is it just that nobody has found the time to implement it?
> If it is the latter, I am willing to implement it as long there is a
> chance to get this accepted into the mainstream kernel.
Well, there's fam. But AFAIK that's all done in user space, and your
approach would be significantly more efficient (as a matter of fact, fam
could be modified to use your change device as a first level of
notification.)
I'll be interested in testing this, or (if you wish) help get it done.
I'm a kernel hacking newbie at the moment, but I have tinkered around
enough with the VFS to be able to work on this. Up to you.
--
Javier Fernandez-Ivern
next prev parent reply other threads:[~2003-12-31 18:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-31 16:42 Rüdiger Klaehn
2003-12-31 18:20 ` Javier Fernandez-Ivern [this message]
2003-12-31 18:48 ` Rüdiger Klaehn
2004-01-01 1:28 ` Michael Clark
2004-01-01 1:58 ` Dave Jones
2004-01-01 2:18 ` Michael Clark
2004-01-01 2:30 ` Javier Fernandez-Ivern
2004-01-01 13:11 ` Rüdiger Klaehn
2003-12-31 20:49 ` Javier Fernandez-Ivern
2004-01-01 9:02 ` Juergen Hasch
2004-01-01 10:47 ` jw schultz
2004-01-01 12:44 ` Rüdiger Klaehn
2004-01-03 6:32 ` Jan Harkes
-- strict thread matches above, loose matches on Subject: below --
2004-02-07 8:29 John Ogness
2004-02-07 14:01 ` Christoph Hellwig
[not found] <18PG9-4og-27@gated-at.bofh.it>
[not found] ` <18TgF-QJ-7@gated-at.bofh.it>
[not found] ` <18TJE-1qL-3@gated-at.bofh.it>
2003-12-31 19:30 ` René Scharfe
2002-11-01 21:31 file " Colin Burnett
2002-11-01 22:19 ` Chris Wright
2002-11-02 15:43 ` Jamie Lokier
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=3FF31366.30206@acm.org \
--to=ivern@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rudi@lambda-computing.de \
--cc=viro@math.psu.edu \
/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
Powered by JetHome