From: "Juan J. Quintela" <quintela@fi.udc.es>
To: vii@penguinpowered.com
Cc: linux-mm@kvack.org
Subject: Re: 2.4 / 2.5 VM plans
Date: 28 Jun 2000 23:04:45 +0200 [thread overview]
Message-ID: <yttog4lwm8i.fsf@serpe.mitica> (raw)
In-Reply-To: vii@penguinpowered.com's message of "28 Jun 2000 18:45:46 +0100"
>>>>> "vii" == vii <vii@penguinpowered.com> writes:
Hi
>> 3) separate page replacement (page aging) and page flushing,
vii> Definitely!
I have done part of this work with my write deferred swap (I will port
it to test3 ASAP). The deferred swap write also helps. It is related
with your question about removing swap_out function, it is related
with the scanning and the several lists setup.
vii> BTW, Is there any timescale for integrating page coloring? Someone
vii> produced a patch somewhere (IIRC specifically for the alpha, sorry to
vii> be so vague).
There was a page colouring patch frem somone at DEC^WCompaq, and
another one from David Miller. The one from Compaq appeared to have
some problems with some workloads (see the comments from Dave Miller,
I think in this list). I haven't seen the David one, I can't comment
on that. But I suppose that the integration will be a 2.5 thing
(Wild, wild guess).
Later, Juan.
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
--
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:[~2000-06-28 21:04 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
2000-06-28 21:04 ` Juan J. Quintela [this message]
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=yttog4lwm8i.fsf@serpe.mitica \
--to=quintela@fi.udc.es \
--cc=linux-mm@kvack.org \
--cc=vii@penguinpowered.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