[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070711204143.GA3921@ucw.cz>
Date: Wed, 11 Jul 2007 20:41:44 +0000
From: Pavel Machek <pavel@....cz>
To: Al Viro <viro@....linux.org.uk>
Cc: Andi Kleen <andi@...stfloor.org>, Ingo Molnar <mingo@...e.hu>,
Andrew Morton <akpm@...ux-foundation.org>,
Frank Kingswood <frank@...gswood-consulting.co.uk>,
Nick Piggin <nickpiggin@...oo.com.au>,
Ray Lee <ray-lk@...rabbit.org>,
Jesper Juhl <jesper.juhl@...il.com>,
ck list <ck@....kolivas.org>, Paul Jackson <pj@....com>,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: RFT: updatedb "morning after" problem [was: Re: -mm merge plans for 2.6.23]
Hi!
> > That would just save reading the directories. Not sure
> > it helps that much. Much better would be actually if it didn't stat the
> > individual files (and force their dentries/inodes in). I bet it does that to
> > find out if they are directories or not. But in a modern system it could just
> > check the type in the dirent on file systems that support
> > that and not do a stat. Then you would get much less dentries/inodes.
>
> FWIW, find(1) does *not* stat non-directories (and neither would this
> approach). So it's just dentries for directories and you can't realistically
> skip those. OK, you could - if you had banned cross-directory rename
> for directories and propagated "dirty since last look" towards root (note
> that it would be a boolean, not a timestamp). Then we could skip unchanged
> subtrees completely...
Could we help it a little from kernel and set 'dirty since last look'
on directory renames?
I mean, this is not only updatedb. KDE startup is limited by this,
too. It would be nice to have effective 'what change in tree'
operation.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists