Re: Ongoing 2.4 VM suckage

[Mike Black]

I floated this idea a while ago but didn't receive any comments (or
flames)...
Couldn't kswapd just gracefully back-off when it doesn't make any progress?
In my case (with ext3/raid5 and a tiobench test) kswapd NEVER actually swaps
anything out.
It just chews CPU time.
So...if kswapd just said "didn't make any progress...*2 last sleep" so it
would degrade itself.
Doesn't sound like a major rewrite to me.

----- Original Message -----
From: "Rik van Riel" <[e-mail]>
To: "David Ford" <[e-mail]>
Cc: "Jeffrey W. Baker" <[e-mail]>; "Richard B. Johnson"
<[e-mail]>; <[e-mail]>
Sent: Friday, August 03, 2001 4:53 PM
Subject: Re: Ongoing 2.4 VM suckage

> On Fri, 3 Aug 2001, David Ford wrote:
>
> > If it is that badly broken, isn't that sufficient criteria to justify
> > the patch?
>
> It's not just a patch. Fixing this problem will require
> a major VM rewrite. A rewrite I really wasn't willing
> to make for 2.4.
>
> I'll start writing the thing, but I won't be aiming at
> getting it included in 2.4. I guess I could code it in
> such a way to give a drop-in replacement for people
> willing to cut themselves on the bleeding edge, though ;)
>
> Rik
> --
> Virtual memory is like a game you can't win;
> However, without VM there's truly nothing to lose...
>
> http://www.surriel.com/ http://distro.conectiva.com/
>
> Send all your spam to [e-mail] (spam digging piggy)
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [e-mail]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/