From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: 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 10:55:42 +1100 [thread overview]
Message-ID: <1072482941.15458.90.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.58.0312260957100.14874@home.osdl.org>
> Yeah, all hail bad MMU's.
Bad MMUs or our architetured beeing tied to one MMU type ? :)
(Note that I'm no special fan of our PPC hash table, it seems
to be fairly bad with the cache).
Note also that the need for a flush isn't tied to that fact we
have a hash table but to how we use it in linux. If we used the
real HW A and D bits and had ptep_test_and_clear* actually walk
the hash and use them, we could avoid the flush the same way in
this case.
But we do not, we use the hash as a big TLB cache and consider
any page in there as accessed and any writeable page in there as
diry, so clearing those bits requires evicting from the hash
(hash misses, at least on ppc32, are fairly cheap though).
> Hash tables may need some kind of "not very urgent TLB flush" thing, so
> that it doesn't penalize sane architectures.
Or do what I propose here, that is have ptep_test_and_clear_* be
responsible for the flush on archs where it is necessary, but then
it would be nice to have more than the ptep as an argument...
Ben.
next prev parent reply other threads:[~2003-12-26 23:56 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 [this message]
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
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=1072482941.15458.90.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.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