From: Al Viro <viro@ZenIV.linux.org.uk>
To: Jan Kara <jack@suse.cz>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>,
linux-kernel@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Thomas Rast <trast@inf.ethz.ch>, Duy Nguy???n <pclouds@gmail.com>,
Jeff King <peff@peff.net>,
Karsten Blees <karsten.blees@gmail.com>
Subject: Re: Beyond inotify recursive watches
Date: Fri, 5 Apr 2013 17:12:29 +0100 [thread overview]
Message-ID: <20130405161229.GC4068@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20130405155534.GC21852@quack.suse.cz>
On Fri, Apr 05, 2013 at 05:55:34PM +0200, Jan Kara wrote:
> What your question reminds me is an idea of recursive modification time
> stamp on directories. That is a time stamp that gets updated whenever
> anything in the tree under the directory changes. Now this would be too
> expensive to maintain so there's also a trick implemented that you update
> the time stamp (and continue updating recursive time stamps upwards) only
> if a special flag is set on the directory. And you clear the flag at that
> moment. So until someone checks the time stamp and resets the flag no
> further updates of the recursive modification time happen.
>
> This scheme works for arbitrary number of processes interested in recursive
> time stamps (only updates of the time stamps get more frequent). What is
> somewhat inconvenient is that this only tells you something in the
> directory or its subtree changed so you still have to scan all the
> directories on the path to modified file. So I'm not sure of how much use
> this would be to you.
Feel free to write up the details of locking you'll need for that. It will
*not* be fun...
next prev parent reply other threads:[~2013-04-05 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 10:48 Ramkumar Ramachandra
2013-04-05 15:55 ` Jan Kara
2013-04-05 16:12 ` Al Viro [this message]
2013-04-08 9:31 ` Jan Kara
2013-04-10 18:36 ` Ramkumar Ramachandra
2013-04-10 20:40 ` Jan Kara
2013-04-11 11:59 ` Ramkumar Ramachandra
2013-04-11 21:02 ` Jan Kara
2013-04-05 16:56 ` Ramkumar Ramachandra
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=20130405161229.GC4068@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=artagnon@gmail.com \
--cc=gitster@pobox.com \
--cc=jack@suse.cz \
--cc=karsten.blees@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=trast@inf.ethz.ch \
/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
all inboxes | Powered by JetHome®