[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070725082822.GA13098@elte.hu>
Date: Wed, 25 Jul 2007 10:28:22 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Rene Herman <rene.herman@...il.com>
Cc: Valdis.Kletnieks@...edu, david@...g.hm,
Nick Piggin <nickpiggin@...oo.com.au>,
Ray Lee <ray-lk@...rabbit.org>,
Jesper Juhl <jesper.juhl@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
ck list <ck@....kolivas.org>, Paul Jackson <pj@....com>,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: -mm merge plans for 2.6.23
* Rene Herman <rene.herman@...il.com> wrote:
> Regardless, I'll stand by "[by disabling updatedb] the problem will
> for a large part be solved" as I expect approximately 94.372 percent
> of Linux desktop users couldn't care less about locate.
i think that approach is illogical: because Linux mis-handled a mixed
workload the answer is to ... remove a portion of that workload?
To bring your approach to the extreme: what if Linux sucked at running
more than two CPU-intense tasks at once. Most desktop users dont do
that, so a probably larger than 94.372 percent of Linux desktop users
couldn't care less about a proper scheduler. Still, anyone who builds a
kernel (the average desktop user wont do that) while using firefox will
attest to the fact that it's quite handy that the Linux scheduler can
handle mixed workloads pretty well.
now, it might be the case that this mixed VM/VFS workload cannot be
handled any more intelligently - but that wasnt your argument! The
swap-prefetch patch certainly tried to do things more intelligently and
the test-case (measurement app) Con provided showed visible improvements
in swap-in latency. (and a good number of people posted those results)
Ingo
-
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