mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: Daniel Phillips <phillips@innominate.de>
Cc: "Michael D. Crawford" <crawford@goingware.com>,
	Stephen Rothwell <sfr@linuxcare.com.au>,
	linux-kernel@vger.kernel.org
Subject: Re: FS callback routines
Date: Wed, 10 Jan 2001 11:56:32 +0100	[thread overview]
Message-ID: <20010110115632.E30055@pcep-jamie.cern.ch> (raw)
In-Reply-To: <3A5A4958.CE11C79B@goingware.com> <3A5B0D0C.719E69F@innominate.de>
In-Reply-To: <3A5B0D0C.719E69F@innominate.de>; from phillips@innominate.de on Tue, Jan 09, 2001 at 02:07:24PM +0100

Daniel Phillips wrote:
> It was done last year, quietly and without fanfare, by Stephen Rothwell:
> 
>   http://www.linuxcare.com/about-us/os-dev/rothwell.epl
> 
> This may be the most significant new feature in 2.4.0, as it allows us
> to take a fundamentally different approach to many different problems. 
> Three that come to mind:
[...]
>    mail (get your mail instantly without polling);

You'll be notified if _any_ mailbox is changed in your mail directory.
On a multiuser system that's going to be more often than a typical
polling interval, so you'll have to revert to polling.

> make (don't rely on timestamps to know when rebuilding is needed, don't
> scan huge directory trees on each build)

You will need to rescan the timestamps of files, but yes you can skip
subdirectories in which no file has changed.  But only if you're running
a "make daemon" on the same box as make, and if there aren't too many
directories.

> locate (reindex only those directories that have changed, keep index
> database current).

Not a chance.  dnotify doesn't work recursively, so you can't monitor
just a few top level directories like "/usr/lib".  And have you ever
tried to keep all 3000 directories on your filesystem directories open
at the same time?  Would you want to consume that much non-swappable
memory, and also prevent the directories from being removed from the
filesystem?

Long ago I proposed something similar that works at the disk level, is
recursive, and the checks can be done without keeping directories open.
But I never wrote the code :(  That's interesting because it speeds up
make without needing a daemon, and really can speed up
locate/updatedb/find.

-- Jamie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-10 10:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-08 23:12 Michael D. Crawford
2001-01-09  2:37 ` Sean R. Bright
2001-01-09  3:48 ` David Weinehall
2001-01-09 13:07 ` Daniel Phillips
2001-01-10 10:56   ` Jamie Lokier [this message]
2001-01-10 18:25     ` Daniel Phillips
2001-01-11 14:30     ` Daniel Phillips
2001-01-11 15:37       ` Jamie Lokier
2001-01-11 16:11         ` Daniel Phillips
2001-01-09  1:21 Sean R. Bright
2001-01-09 11:22 ` Philipp Matthias Hahn
2001-01-09 11:34 ` Daniel Stodden
2001-01-09 14:05 Jesse Pollard
2001-01-09 15:41 ` Daniel Phillips
2001-01-10 10:48   ` Jamie Lokier
2001-01-10 15:18 Jesse Pollard
2001-01-11 16:39 Jesse Pollard
2001-01-11 17:53 ` Daniel Phillips

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=20010110115632.E30055@pcep-jamie.cern.ch \
    --to=lk@tantalophile.demon.co.uk \
    --cc=crawford@goingware.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@innominate.de \
    --cc=sfr@linuxcare.com.au \
    /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®