From: James Bottomley <James.Bottomley@SteelEye.com>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Linus Torvalds <torvalds@osdl.org>,
Philippe Robin <Philippe.Robin@arm.com>,
Andrew Morton <akpm@osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Fwd: Re: flush_cache_page()
Date: Sat, 29 Jan 2005 08:29:22 -0600 [thread overview]
Message-ID: <1107008962.4535.8.camel@mulgrave> (raw)
In-Reply-To: <20050129113707.B2233@flint.arm.linux.org.uk>
On Sat, 2005-01-29 at 11:37 +0000, Russell King wrote:
> Thanks for the response. However, apart from Ralph, Paul and yourself,
> it seems none of the other architecture maintainers care about this
> patch - the original mail was BCC'd to the architecture list. Maybe
> that's an implicit acceptance of this patch, I don't know.
Well, OK, I'll try to answer for parisc, since we have huge VIPT
aliasing caches as well.
Right now, we have a scheme in flush_cache_page to make sure it's only
called when necessary (cache flushes are expensive for us and show up as
the primary cpu consumer in all of our profiles). Our scheme is to see
if a translation exists for the page and skip the flush if it doesn't.
Obviously, like MIPS, we're also walking the page tables without
locking...
Looking at the callers of this, it seems it would be very unlikely to
call this with a missing translation, in that case, we can use the pfn
to flush the page through a temporary alias space instead and just take
the odd hit if no translation exists.
> In other words, unless I actually receive some real help from the other
> architecture maintainers on this to address your concerns, ARM version 6
> CPUs with aliasing L1 caches (== >16K) will remain a dead dodo with
> mainline Linux kernels.
I've probably been told and forgotten, but what problems do you have
with your VIPT (Arm 6 is VIPT, not VIVT, right?) cache >16k which we
don't have with our 4MB VIPT caches on pa (which work, but cause us
grief with enormous amounts of flushing)?
James
next prev parent reply other threads:[~2005-01-29 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 22:36 Fwd: Re: flush_cache_page() Russell King
2005-01-12 0:07 ` Linus Torvalds
2005-01-29 11:37 ` Russell King
2005-01-29 14:29 ` James Bottomley [this message]
2005-01-29 16:52 ` Ralf Baechle
2005-01-31 2:38 ` David S. Miller
2005-01-12 15:07 ` Ralf Baechle
2005-01-28 15:19 ` Paul Mundt
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=1107008962.4535.8.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=Philippe.Robin@arm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
--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