linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: vii@penguinpowered.com
To: linux-mm@kvack.org
Subject: Re: 2.4 / 2.5 VM plans
Date: 28 Jun 2000 18:45:46 +0100	[thread overview]
Message-ID: <m2bt0l4s39.fsf@boreas.southchinaseas> (raw)
In-Reply-To: Rik van Riel's message of "Sun, 25 Jun 2000 00:51:42 -0300 (BRST)"

Rik van Riel <riel@conectiva.com.br> writes:

[...]

> To start the discussion, here's my flameba^Wlist of ideas:

Seeing as not much discussion has resulted (if so it missed my
mailbox), I'll stick my neck out to agree.

[...]

> 3) separate page replacement (page aging) and page flushing,

Definitely!

>    currently we'll happily free a referenced clean page just
>    because the unreferenced pages haven't been flushed to disk
>    yet ...   this is very bad since the unreferenced pages often
>    turn out to be things like executable code
> 
>    we could achieve this by augmenting the current MM subsystem
>    with an inactive and scavenge list, in the process splitting

Yes! Please!

IMHO another really cool side-effect will be getting rid of the
vmscan.c:swap_out algorithm (at least as far as I understand).

>    shrink_mmap() into three better readable functions ... I have
>    this mostly done

[...]

BTW, Is there any timescale for integrating page coloring? Someone
produced a patch somewhere (IIRC specifically for the alpha, sorry to
be so vague).

-- 

	http://altern.org/vii
--
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-06-28 17:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-25  3:51 Rik van Riel
2000-06-28 17:45 ` vii [this message]
2000-06-28 21:04   ` Juan J. Quintela
2000-06-28 21:17 ` Juan J. Quintela
2000-06-29 13:45   ` Stephen C. Tweedie
2000-06-29 13:44 ` Stephen C. Tweedie
2000-07-06  7:51   ` page_table_lock problem [was: Re: 2.4 / 2.5 VM plans] Andrey Savochkin
2000-07-06 13:32     ` Stephen C. Tweedie

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=m2bt0l4s39.fsf@boreas.southchinaseas \
    --to=vii@penguinpowered.com \
    --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