[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46A6D8DF.8060205@yahoo.com.au>
Date: Wed, 25 Jul 2007 15:00:15 +1000
From: Nick Piggin <nickpiggin@...oo.com.au>
To: Rene Herman <rene.herman@...il.com>
CC: Ray Lee <ray-lk@...rabbit.org>,
Jesper Juhl <jesper.juhl@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
ck list <ck@....kolivas.org>, Ingo Molnar <mingo@...e.hu>,
Paul Jackson <pj@....com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: -mm merge plans for 2.6.23
Rene Herman wrote:
> On 07/25/2007 06:06 AM, Nick Piggin wrote:
>
>> Ray Lee wrote:
>
>
>>> Anyway, my point is that I worry that tuning for an unusual and
>>> infrequent workload (which updatedb certainly is), is the wrong way
>>> to go.
>>
>>
>> Well it runs every day or so for every desktop Linux user, and it has
>> similarities with other workloads.
>
>
> It certainly doesn't run for me ever. Always kind of a "that's not the
> point" comment but I just keep wondering whenever I see anyone complain
> about updatedb why the _hell_ they are running it in the first place. If
> anyone who never uses "locate" for anything simply disable updatedb, the
> problem will for a large part be solved.
>
> This not just meant as a cheap comment; while I can think of a few
> similar loads even on the desktop (scanning a browser cache, a media
> player indexing a large amount of media files, ...) I've never heard of
> problems _other_ than updatedb. So just junk that crap and be happy.
OK fair point, but the counter point that there are real patterns
that just use-once a lot of metadata (ls, for example. grep even.)
--
SUSE Labs, Novell Inc.
-
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