From: "Dr. Werner Fink" <werner@suse.de>
To: Linux MM <linux-mm@kvack.org>
Subject: Re: TODO list, v0.01
Date: Mon, 15 Jun 1998 18:56:47 +0200 [thread overview]
Message-ID: <19980615185647.50925@boole.suse.de> (raw)
In-Reply-To: <Pine.LNX.3.95.980611235823.21729A-100000@localhost>; from Rik van Riel on Thu, Jun 11, 1998 at 11:59:45PM +0200
On Thu, Jun 11, 1998 at 11:59:45PM +0200, Rik van Riel wrote:
>
> here's the MM TODO list, very first version, just listing
> the projects people are working on.
>
> Other projects are yet to be added -- what ones?
>
> Rik.
[...]
>
> Werner Fink <werner@suse.de>
>
> ???
>
??? == We should get a better recover time/behaviour of the mm for small
systems under high load. Currently small systems with 2.1.10X
(RAM < 32MB, sometimes < 64MB) do loose in comparision to 2.0.33/34.
Werner
next prev parent reply other threads:[~1998-06-15 16:57 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
1998-06-15 16:56 ` Dr. Werner Fink [this message]
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=19980615185647.50925@boole.suse.de \
--to=werner@suse.de \
--cc=linux-mm@kvack.org \
/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