From: William Lee Irwin III <wli@holomorphy.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linus Torvalds <torvalds@osdl.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Rik van Riel <riel@surriel.com>, Andrew Morton <akpm@osdl.org>
Subject: Re: Page aging broken in 2.6
Date: Sat, 27 Dec 2003 02:16:55 -0800 [thread overview]
Message-ID: <20031227101655.GJ27687@holomorphy.com> (raw)
In-Reply-To: <20031227023752.GF1676@dualathlon.random>
On Sat, Dec 27, 2003 at 03:37:53AM +0100, Andrea Arcangeli wrote:
> It's hard for me to evaluate how much the young bit matters by only
> thinking about it, I know for sure the heavily swapping behaviour on
> the alpha was noticeably less smooth than on x86 (alpha has^Hd no way to
> implement the young bit, not even like you do in software through hash
> faults). So I guess it's worthwhile for you to account for it even if in
> software (i.e. ppc not ppc64).
I have a vague notion it should be possible to turn off the PAL
pagetable emulation and do these things yourself, though I'm not
entirely clear on how practical this is to do (e.g. whether the real
MMU's docs are public, whether the PAL code can be turned off at all,
etc.). It would be a relatively large amount of arch code to bang out,
and for a largely (and rather unfortunately) dead architecture at that.
Probably a moot point depending on the level of resistance to the idea
(which seems to dominate technical concerns for a number of things) and
how thin I'm spread. I've got a multia, but (a) multias suck and (b)
it's stripped, so unless I feel like debugging swapping over the network,
that's useless apart from making sure it boots and runs luserspace.
I guess the point of this was really a roundabout way to ask if there
was enough information to either do that with or rule it out just to
satisfy my own curiosity, since it's not likely I'll ever get around
to actually trying to implement it.
-- wli
next prev parent reply other threads:[~2003-12-27 10:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-26 7:28 Page aging broken in 2.6 Benjamin Herrenschmidt
2003-12-26 7:40 ` Andrew Morton
2003-12-26 9:21 ` Arjan van de Ven
2003-12-26 9:58 ` Benjamin Herrenschmidt
2003-12-26 19:44 ` Davide Libenzi
2003-12-26 9:33 ` Russell King
2003-12-26 10:07 ` Benjamin Herrenschmidt
2003-12-26 17:59 ` Linus Torvalds
2003-12-26 23:55 ` Benjamin Herrenschmidt
2003-12-27 0:35 ` Linus Torvalds
2003-12-27 0:44 ` Benjamin Herrenschmidt
2003-12-27 0:53 ` Linus Torvalds
2003-12-27 0:59 ` Linus Torvalds
2003-12-27 1:03 ` Benjamin Herrenschmidt
2003-12-27 2:37 ` Andrea Arcangeli
2003-12-27 5:02 ` Benjamin Herrenschmidt
2003-12-27 10:16 ` William Lee Irwin III [this message]
2003-12-27 2:47 ` Rik van Riel
2003-12-27 3:00 ` Andrew Morton
2003-12-27 3:31 ` Rik van Riel
2003-12-27 3:54 ` Linus Torvalds
2003-12-27 16:34 ` Martin J. Bligh
2003-12-27 23:07 ` Roger Luethi
2003-12-27 23:55 ` William Lee Irwin III
2003-12-28 11:23 ` Roger Luethi
2003-12-28 16:35 ` William Lee Irwin III
2003-12-28 17:15 ` Roger Luethi
2003-12-28 0:04 ` Andrew Morton
2003-12-28 11:58 ` Roger Luethi
2003-12-27 1:41 ` Andrea Arcangeli
-- strict thread matches above, loose matches on Subject: below --
2003-12-26 10:45 Manfred Spraul
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=20031227101655.GJ27687@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@surriel.com \
--cc=torvalds@osdl.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