From: John McCutchan <ttb@tentacle.dhs.org>
To: Chris Wedgwood <cw@f00f.org>
Cc: nautilus-list@gnome.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC/PATCH] inotify -- a dnotify replacement
Date: Tue, 11 May 2004 08:20:01 -0400 [thread overview]
Message-ID: <1084278001.1225.9.camel@vertex> (raw)
In-Reply-To: <20040511024701.GA19489@taniwha.stupidest.org>
On Mon, 2004-05-10 at 22:47, Chris Wedgwood wrote:
> On Mon, May 10, 2004 at 06:17:40PM -0400, John McCutchan wrote:
>
> > According to everyone who uses dnotify it is.
>
> I don't buy that. I have used dnotify and signals where not an issue.
> Why is this an issue for others?
>
Signals cause a big performance penalty when you are receiving a lot of
them. Signals interrupt your program, switch the signal handler and then
restarts your program. And signals in multi-threaded programs is a pain
as well. Signals just are not suitable for receiving lots of messages
quickly.
> > > 3) dnotify cannot easily watch changes for a directory hierarchy
>
> > People don't seem to really care about this one. Alexander Larsson
> > has said he doesn't care about it. It might be nice to add in the
> > future.
>
> I don't know who that is and why it matters.
>
> Without being able to watch a hierarchy, I'm not sure inotify buys
> anything that we can't get from dnotify right now though. It's also
> more complex.
Inotify will support watching a hierarchy. The reason it was not
implemented yet is because the one app that I really care about is
nautilus and the maintainer of it says he doesn't care.
The big feature that inotify is trying to provide is not having to keep
a file open (So that unmounting is not affected). I asked for some
guidance from people more familiar with the kernel so that I can
implement this feature, it requires changes made to the inode cache, and
how unmounting is done.
>
> > The idea is to encourage use of a user-space daemon that will
> > multiplex all requests, so if 5 people want to watch /somedir the
> > daemon will only use one watcher in the kernel. The number might be
> > too low, but its easily upped.
>
> If you are to use a daemon for this, why no use dnotify?
Because of the problems that dnotify has, as well if people would prefer
to just use a direct interface, those #defines can be upped. Its very
easy to play with the limits on the number of watchers. I am not sure
what kind of impact this will have on the kernel resources, so I wanted
to keep it small.
John
next prev parent reply other threads:[~2004-05-11 12:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 1:35 [RFC/PATCH] inotify -- a dnotify replacement John McCutchan
2004-05-10 2:11 ` Chris Wedgwood
2004-05-10 22:17 ` John McCutchan
2004-05-10 22:31 ` Davide Libenzi
2004-05-10 22:41 ` John McCutchan
2004-05-10 22:52 ` Davide Libenzi
2004-05-10 23:10 ` Valdis.Kletnieks
2004-05-10 23:42 ` Davide Libenzi
2004-05-11 4:11 ` Chris Wedgwood
2004-05-11 2:00 ` Ian Kent
2004-05-11 2:47 ` Chris Wedgwood
2004-05-11 11:52 ` nf
2004-05-11 12:17 ` Stephen Rothwell
2004-05-11 12:24 ` John McCutchan
[not found] ` <1084278605.3839.47.camel@carados.180sw.com>
[not found] ` <1084885604.4062.48.camel@lilota.lamp.priv>
[not found] ` <1085127066.20393.440.camel@localhost.localdomain>
2004-05-21 12:04 ` nf
2004-05-11 12:20 ` John McCutchan [this message]
2004-05-11 12:46 ` viro
2004-05-11 19:02 ` John McCutchan
2004-05-11 20:28 ` carbonated beverage
2004-05-11 21:28 ` John McCutchan
2004-05-11 15:02 ` Alexander Larsson
2004-05-11 21:41 ` Chris Wedgwood
2004-05-12 12:38 ` Jörn Engel
2004-05-13 15:36 ` raven
2004-05-13 19:04 ` Chris Wedgwood
2004-05-14 7:04 ` Ian Kent
2004-05-13 21:24 ` John McCutchan
2004-05-14 2:02 ` Ian Kent
2004-05-15 4:52 ` raven
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=1084278001.1225.9.camel@vertex \
--to=ttb@tentacle.dhs.org \
--cc=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nautilus-list@gnome.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.