From: Rik van Riel <riel@conectiva.com.br>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.redhat.com,
Linus Torvalds <torvalds@transmeta.com>,
Matthew Dillon <dillon@apollo.backplane.com>
Subject: TODO list for new VM
Date: Sat, 16 Sep 2000 06:13:27 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.21.0009160544000.1519-100000@duckman.distro.conectiva> (raw)
Hi,
Here is the TODO list for the new VM. The only thing
really needed for 2.4 is the OOM handler and the
page->mapping->flush() callback is really wanted by
the journaling filesystem folks.
The rest are mostly extra's that would be nice; these
things won't be pushed for inclusion except if it turns
out to be really trivial to implement, high performance
on the cases they're supposed to affect and their influence
is highly localised...
(sorry folks, but for 2.4 I'll be really conservative)
---> TODO list for the new VM <---
for kernel 2.4, necessary:
- out of memory handling
[integrate the OOM killer, 10 minutes work]
for kernel 2.4, really wanted:
- page->mapping->flush() callback in page_launder(),
for easier integration with journaling filesystems
and maybe the network filesystems
[about 30 minutes of work on the VM side]
for kernel 2.4, wanted:
- include Ben LaHaise's code, which moves readahead
to the VMA level, this way we can do streaming swap
IO, complete with drop_behind()
- code to make the "knee" smoother, currently the system
keeps eating memory from the cache up to a certain point
and then starts to swap a lot, it would be nice to smooth
this curve a bit
- thrashing control, maybe process suspension with some
forced swapping ?
for kernel 2.5:
- physical->virtual reverse mapping, so we can do much
better page aging with less CPU usage spikes
- better IO clustering for swap (and filesystem) IO
- move all the global VM variables, lists, etc. into
the pgdat struct for better NUMA scalability
- (maybe) some QoS things, as far as they are major
improvements with minor intrusion
regards,
Rik
--
"What you're running that piece of shit Gnome?!?!"
-- Miguel de Icaza, UKUUG 2000
http://www.conectiva.com/ http://www.surriel.com/
--
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/
reply other threads:[~2000-09-16 9:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.4.21.0009160544000.1519-100000@duckman.distro.conectiva \
--to=riel@conectiva.com.br \
--cc=dillon@apollo.backplane.com \
--cc=linux-kernel@vger.redhat.com \
--cc=linux-mm@kvack.org \
--cc=torvalds@transmeta.com \
/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