From: "Stephen C. Tweedie" <sct@redhat.com>
To: Paul Barton-Davis <pbd@Op.Net>
Cc: "Theodore Y. Ts'o" <tytso@MIT.EDU>,
linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Subject: Re: a joint letter on low latency and Linux
Date: Mon, 3 Jul 2000 12:06:36 +0100 [thread overview]
Message-ID: <20000703120636.B2931@redhat.com> (raw)
In-Reply-To: <200006301506.LAA12457@renoir.op.net>; from pbd@Op.Net on Fri, Jun 30, 2000 at 11:03:08AM -0400
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/
parent reply other threads:[~2000-07-03 11:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200006301506.LAA12457@renoir.op.net>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20000703120636.B2931@redhat.com \
--to=sct@redhat.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=pbd@Op.Net \
--cc=tytso@MIT.EDU \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox