* Re: a joint letter on low latency and Linux
[not found] ` <200006301506.LAA12457@renoir.op.net>
@ 2000-07-03 11:06 ` Stephen C. Tweedie
0 siblings, 0 replies; only message in thread
From: Stephen C. Tweedie @ 2000-07-03 11:06 UTC (permalink / raw)
To: Paul Barton-Davis; +Cc: Theodore Y. Ts'o, linux-kernel, linux-mm
Hi,
On Fri, Jun 30, 2000 at 11:03:08AM -0400, Paul Barton-Davis wrote:
> Well, I'm sympathetic to this. But just yesterday, I saw Stephen
> Tweedie saying that the VM system needed another fairly significant
> redesign begore it could be considered ready for 2.4.0.
It needs some really careful thinking, and a small (though still
significant) amount of reworking of *highly* localised functions
before 2.4. It also needs a complete overhaul, but that's a 2.5
issue. For 2.4 the objective has to be minimum necessary change. The
trouble is that 2.4 VM performance has sufficiently bad worst case
behaviour right now that some change is necessary --- the existing
behaviour is a serious bug needing fixed.
It is too late to change the VM mechanisms for 2.4, but the policy
code still needs a good, hard think, since we currently perform much
much worse than 2.2 at some jobs.
It IS too late to add features over and above what we already have in
the source tree. That's why we've got a substantial wish-list of
experimental stuff to explore for the 2.5 VM in addition to the fixes
needed for 2.4.
--Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2000-07-03 11:06 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <200006301310.JAA06222@tsx-prime.MIT.EDU>
[not found] ` <200006301506.LAA12457@renoir.op.net>
2000-07-03 11:06 ` a joint letter on low latency and Linux Stephen C. Tweedie
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox