On Tue, 29 May 2001, Craig Kulesa wrote:
> Mike Galbraith ([EMAIL PROTECTED]) wrote:
> >
> > Emphatic yes. We went from cache collapse to cache bloat.
>
> Rik, I think Mike deserves his beer. ;)
:)
...
> So is there an ideal VM balance for everyone? I have found that low-RAM
(I seriously doubt it)
> systems seem to benefit from being on the "cache-collapse" side of the
> curve (so I prefer the pre-2.4.5 balance more than Mike probably does) and
I hate both bad behaviors equally. "cache bloat" hurts more people
than "cache collapse" does though because it shows under light load.
> those low-RAM systems are the first hit when, as now, we're favoring
> "cache bloat". Should balance behaviors could be altered by the user
> (via sysctl's maybe? Yeah, I hear the cringes)? Or better, is it
> possible to dynamically choose where the watermarks in balancing should
> lie, and alter them automatically? 2.5 stuff there, no doubt. Balancing
> seems so *fragile* (to me).
The page aging logic does seems fragile as heck. You never know how
many folks are aging pages or at what rate. If aging happens too fast,
it defeats the garbage identification logic and you rape your cache. If
aging happens too slowly...... sigh.
-Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
