From: Rik van Riel <H.H.vanRiel@phys.uu.nl>
To: "Stephen C. Tweedie" <sct@dcs.ed.ac.uk>
Cc: Rik van Riel <H.H.vanRiel@phys.uu.nl>, Linux MM <linux-mm@kvack.org>
Subject: Re: TODO list, v0.01
Date: Sat, 13 Jun 1998 08:15:33 +0200 (MET DST) [thread overview]
Message-ID: <Pine.LNX.3.95.980613081315.3680B-100000@localhost> (raw)
In-Reply-To: <199806122247.XAA02295@dax.dcs.ed.ac.uk>
On Fri, 12 Jun 1998, Stephen C. Tweedie wrote:
> On Thu, 11 Jun 1998 23:59:45 +0200 (MET DST), Rik van Riel
> <H.H.vanRiel@phys.uu.nl> said:
>
> > Other projects are yet to be added -- what ones?
>
> Lots --- mainly sorting out performance and fragmentation issues for
> 2.2 in the short term. More after Usenix...
The fragmentation issue will get better when I have written
the new allocator. When I keep it simple and really trivial
I might even convince Linus to merge it in a stable release.
The performance will mainly need swapin readahead. I've
found swapout to be quite fast already.
The other performance issue is with multiple scanning of
shared pages, which will be fixed for free once the PTE
chaining of you and Ben is done...
Rik.
+-------------------------------------------------------------------+
| Linux memory management tour guide. H.H.vanRiel@phys.uu.nl |
| Scouting Vries cubscout leader. http://www.phys.uu.nl/~riel/ |
+-------------------------------------------------------------------+
next prev parent reply other threads:[~1998-06-13 6:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-11 21:59 Rik van Riel
1998-06-12 22:47 ` Stephen C. Tweedie
1998-06-13 6:15 ` Rik van Riel [this message]
1998-06-15 16:56 ` Dr. Werner Fink
1998-06-16 15:11 ` Stephen Tweedie
1998-06-16 19:04 ` Rik van Riel
[not found] <19980613020130.B412@uni-koblenz.de>
1998-06-13 6:36 ` Rik van Riel
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=Pine.LNX.3.95.980613081315.3680B-100000@localhost \
--to=h.h.vanriel@phys.uu.nl \
--cc=linux-mm@kvack.org \
--cc=sct@dcs.ed.ac.uk \
/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