From: Daniel Veillard <veillard@redhat.com>
To: John McCutchan <ttb@tentacle.dhs.org>
Cc: linux-kernel@vger.kernel.org, nautilus-list@gnome.org
Subject: Re: [PATCH] inotify 0.5
Date: Sun, 18 Jul 2004 23:37:19 -0400 [thread overview]
Message-ID: <20040719033719.GA24114@redhat.com> (raw)
In-Reply-To: <1090180167.5079.21.camel@vertex>
On Sun, Jul 18, 2004 at 03:49:27PM -0400, John McCutchan wrote:
[...]
> I have attached a tarball, which includes the patch for linux 2.6.7 and
> a small test app.
>
> I have tested this on my system and AFAIK it is working. No doubt it has
> plenty of bugs.
>
> I plan on adding an inotify backend to gamin soon.
I take patches :-)
But I think it misses the really good point of inotify as I see
it, i.e. there is no need anymore of a daemon outside the application
space, in practice I would rather see inotify plugged at the gnome-vfs
level. The reason is that you will just need to monitor the inotify
file descriptor, which is easy to do at the gnome-vfs level since you
have glib and loop access, while in libgamin this would either require
disabling dnotify if inotify is available (FAM has only one fd registered
at the application layer), or use the daemon for inotify too.
The only advantage of using the daemon would be for advanced features
like congestion control, which are not available (yet ?) in gamin.
inotify sounds good to me, I hope it won't be bounced by the kernels
people.
Daniel
--
Daniel Veillard | Red Hat Desktop team http://redhat.com/
veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
prev parent reply other threads:[~2004-07-19 3:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-18 19:49 [PATCH] inotify 0.5 John McCutchan
2004-07-18 19:53 ` Martin Schlemmer
2004-07-18 20:02 ` John McCutchan
2004-07-18 20:11 ` Martin Schlemmer
2004-07-18 20:22 ` John McCutchan
2004-07-18 23:37 ` Davide Libenzi
2004-07-19 1:42 ` John McCutchan
2004-07-19 8:43 ` Ian Kent
2004-07-19 13:33 ` Chris Friesen
2004-07-19 21:31 ` John McCutchan
2004-07-20 2:59 ` Eric Lammerts
2004-07-20 3:24 ` John McCutchan
2004-07-20 1:33 ` Ian Kent
2004-07-19 3:37 ` Daniel Veillard [this message]
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=20040719033719.GA24114@redhat.com \
--to=veillard@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nautilus-list@gnome.org \
--cc=ttb@tentacle.dhs.org \
/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