From: afei@jhu.edu
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: MM/VM todo list
Date: Mon, 08 Jan 2001 12:31:39 -0500 (EST) [thread overview]
Message-ID: <Pine.GSO.4.05.10101081230560.23656-100000@aa.eps.jhu.edu> (raw)
In-Reply-To: <Pine.LNX.4.21.0101051505430.1295-100000@duckman.distro.conectiva>
About the RSS ulimit proposal, have we resolved the correctness of
counting RSS in a process?
Fei
On Fri, 5 Jan 2001, Rik van Riel wrote:
> Hi,
>
> here is a TODO list for the memory management area of the
> Linux kernel, with both trivial things that could be done
> for later 2.4 releases and more complex things that really
> have to be 2.5 things.
>
> Most of these can be found on http://linux24.sourceforge.net/ too
>
> Trivial stuff:
> * VM: better IO clustering for swap (and filesystem) IO
> * Marcelo's swapin/out clustering code
> * ->writepage() IO clustering support
> * page_launder()/->writepage() working together in avoiding
> low-yield (small cluster) IO at first, ...
> * VM: include Ben LaHaise's code, which moves readahead to the
> VMA level, this way we can do streaming swap IO, complete with
> drop_behind()
> * VM: enforce RSS ulimit
>
>
> Probably 2.5 era:
> * VM: physical->virtual reverse mapping, so we can do much
> better page aging with less CPU usage spikes
> * VM: move all the global VM variables, lists, etc. into the
> pgdat struct for better NUMA scalability
> * VM: per-node kswapd for NUMA
> * VM: thrashing control, maybe process suspension with some
> forced swapping ? (trivial only in theory)
> * VM: experiment with different active lists / aging pages
> of different ages at different rates + other page replacement
> improvements
> * VM: Quality of Service / fairness / ... improvements
>
>
> Additions to this list are always welcome, I'll put it online
> on the Linux-MM pages (http://www.linux.eu.org/Linux-MM/) soon.
>
> regards,
>
> Rik
> --
> Virtual memory is like a game you can't win;
> However, without VM there's truly nothing to loose...
>
> http://www.surriel.com/
> http://www.conectiva.com/ http://distro.conectiva.com.br/
>
>
> --
> 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/
>
--
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/
next prev parent reply other threads:[~2001-01-08 17:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-05 17:14 Rik van Riel
2001-01-05 15:54 ` Marcelo Tosatti
2001-01-05 17:50 ` Rik van Riel
2001-01-05 16:56 ` Marcelo Tosatti
2001-01-05 21:13 ` Christoph Hellwig
2001-01-05 21:20 ` Rik van Riel
2001-01-05 21:26 ` Christoph Hellwig
2001-01-05 21:27 ` Rik van Riel
2001-01-05 21:34 ` Christoph Hellwig
2001-01-05 21:52 ` Stephen C. Tweedie
2001-01-05 17:58 ` Daniel Phillips
2001-01-08 17:31 ` afei [this message]
2001-01-08 17:36 ` Rik van Riel
2001-01-08 20:23 ` Rasmus Andersen
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.GSO.4.05.10101081230560.23656-100000@aa.eps.jhu.edu \
--to=afei@jhu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
/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