[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1185608893.6394.62.camel@Homer.simpson.net>
Date: Sat, 28 Jul 2007 09:48:13 +0200
From: Mike Galbraith <efault@....de>
To: Daniel Hazelton <dhazelton@...er.net>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>,
Frank Kingswood <frank@...gswood-consulting.co.uk>,
Andi Kleen <andi@...stfloor.org>,
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]
On Fri, 2007-07-27 at 18:51 -0400, Daniel Hazelton wrote:
> Now, once more, I'm going to ask: What is so terribly wrong with swap
> prefetch? Why does it seem that everyone against it says "Its treating a
> symptom, so it can't go in"?
And once again, I personally have nothing against swap-prefetch, or
something like it. I can see how it or something like it could be made
to improve the lives of people who get up in the morning to find their
apps sitting on disk due to memory pressure generated by over-night
system maintenance operations.
The author himself however, says his implementation can't help with
updatedb (though people seem to be saying that it does), or anything
else that leaves memory full. That IMHO, makes it of questionable value
toward solving what people are saying they want swap-prefetch for in the
first place.
I personally don't care if swap-prefetch goes in or not.
-Mike
-
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