From: Alexander Larsson <alexl@redhat.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: John McCutchan <ttb@tentacle.dhs.org>,
Nautilus <nautilus-list@gnome.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC/PATCH] inotify -- a dnotify replacement
Date: 11 May 2004 17:02:42 +0200 [thread overview]
Message-ID: <1084287762.19104.135.camel@localhost.localdomain> (raw)
In-Reply-To: <20040511024701.GA19489@taniwha.stupidest.org>
On Tue, 2004-05-11 at 04: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?
Its the single thing which forces users of dnotify to have an otherwise
useless daemon. Signals are process global resources. As such, a library
can't allocate them, so dnotify can't be used in a library.
> > > 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.
Hierarchical watches are not important to Nautilus, and the lack of them
has not generally been a problem for Gnome. Furthermore, they are
basically impossible to implement in a way that is sane wrt resource
management in the kernel. Unlimited queues in the kernel is an instant
DOS, and if the queue can overflow there is bascially no way to handle
that correctly from userspace without keeping the entire subtree in
memory (and even that breaks in the presence of aliases).
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Alexander Larsson Red Hat, Inc
alexl@redhat.com alla@lysator.liu.se
He's a gun-slinging pirate gangster on the hunt for the last specimen of a
great and near-mythical creature. She's a manipulative winged Hell's Angel who
can talk to animals. They fight crime!
next prev parent reply other threads:[~2004-05-11 15:02 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
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 [this message]
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=1084287762.19104.135.camel@localhost.localdomain \
--to=alexl@redhat.com \
--cc=cw@f00f.org \
--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