From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Robert Love <rml@novell.com>
Cc: Bill Davidsen <davidsen@tmr.com>, Jan Kara <jack@suse.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] inotify 0.9
Date: Fri, 17 Sep 2004 00:35:52 +0100 [thread overview]
Message-ID: <1095377752.23913.3.camel@localhost.localdomain> (raw)
In-Reply-To: <1095376979.23385.176.camel@betsy.boston.ximian.com>
On Gwe, 2004-09-17 at 00:22, Robert Love wrote:
> The thing you are missing is that you absolutely have to pin something
> or you have multiple VFS races. Your bitmap suggestion, while cute,
> really shows a lack of understanding of the problem space.
How many of the races matter. There seem to be several different
problems here and mixing them up might be a mistake.
1. I absolutely need to get the right file at the right moment, please
mass me a descriptor to the file as the user closes it so I always get
it right (indexer, virus checker)
2. If something happens bug me and I'll have a look (eg file manager)
Also it varies between "This file" and "everything in this subtree".
An indexer for example really wants to know "this file, this path" for
entire subtrees and to index the right object (if the path changes thats
less of an issue).
Alan
next prev parent reply other threads:[~2004-09-17 0:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 15:52 [RFC][PATCH] inotify 0.9 John McCutchan
2004-09-15 18:00 ` Robert Love
2004-09-16 15:07 ` Bill Davidsen
2004-09-16 16:27 ` Chris Friesen
2004-09-16 22:48 ` Bill Davidsen
2004-09-16 16:39 ` Robert Love
2004-09-20 20:16 ` Bill Davidsen
2004-09-20 21:05 ` Robert Love
2004-09-20 22:59 ` Bill Davidsen
2004-09-21 0:02 ` Robert Love
2004-09-16 16:46 ` Jan Kara
2004-09-16 22:34 ` Bill Davidsen
2004-09-16 22:57 ` David Lang
2004-09-16 23:22 ` Robert Love
2004-09-16 23:35 ` Alan Cox [this message]
2004-09-17 2:29 ` Robert Love
2004-09-17 3:08 ` Nicholas Miell
2004-09-17 14:39 ` Alan Cox
2004-09-17 15:48 ` Robert Love
2004-09-17 14:51 ` Alan Cox
2004-09-17 15:55 ` Robert Love
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=1095377752.23913.3.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=davidsen@tmr.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@novell.com \
/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