From: Daniel Phillips <phillips@innominate.de>
To: Rik van Riel <riel@conectiva.com.br>, linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: MM/VM todo list
Date: Fri, 5 Jan 2001 18:58:22 +0100 [thread overview]
Message-ID: <01010519042301.00517@gimli> (raw)
In-Reply-To: <Pine.LNX.4.21.0101051505430.1295-100000@duckman.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0101051505430.1295-100000@duckman.distro.conectiva>
On Fri, 05 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.
I'd like to suggest variable sized pages as a research topic. It's not
clear whether we're talking 2.5 or 2.7 here.
--
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Phillips <phillips@innominate.de>
To: Rik van Riel <riel@conectiva.com.br>, linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: MM/VM todo list
Date: Fri, 5 Jan 2001 18:58:22 +0100 [thread overview]
Message-ID: <01010519042301.00517@gimli> (raw)
In-Reply-To: <Pine.LNX.4.21.0101051505430.1295-100000@duckman.distro.conectiva>
On Fri, 05 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.
I'd like to suggest variable sized pages as a research topic. It's not
clear whether we're talking 2.5 or 2.7 here.
--
Daniel
--
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-05 18:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-05 17:14 MM/VM todo list Rik van Riel
2001-01-05 17:14 ` Rik van Riel
2001-01-05 15:54 ` Marcelo Tosatti
2001-01-05 15:54 ` Marcelo Tosatti
2001-01-05 17:50 ` Rik van Riel
2001-01-05 17:50 ` Rik van Riel
2001-01-05 16:56 ` Marcelo Tosatti
2001-01-05 16:56 ` Marcelo Tosatti
2001-01-05 21:13 ` Christoph Hellwig
2001-01-05 21:13 ` Christoph Hellwig
2001-01-05 21:20 ` Rik van Riel
2001-01-05 21:20 ` Rik van Riel
2001-01-05 21:26 ` Christoph Hellwig
2001-01-05 21:26 ` Christoph Hellwig
2001-01-05 21:27 ` Rik van Riel
2001-01-05 21:27 ` Rik van Riel
2001-01-05 21:34 ` Christoph Hellwig
2001-01-05 21:34 ` Christoph Hellwig
2001-01-05 21:52 ` Stephen C. Tweedie
2001-01-05 21:52 ` Stephen C. Tweedie
2001-01-05 17:58 ` Daniel Phillips [this message]
2001-01-05 17:58 ` Daniel Phillips
2001-01-08 17:31 ` afei
2001-01-08 17:31 ` afei
2001-01-08 17:36 ` Rik van Riel
2001-01-08 17:36 ` Rik van Riel
2001-01-08 20:23 ` Rasmus Andersen
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=01010519042301.00517@gimli \
--to=phillips@innominate.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.