From: David VomLehn <dvomlehn@cisco.com>
To: jfraser@broadcom.com
Cc: Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org, michael.sundius@sciatl.com
Subject: Re: Anyone noticed that there are a lot of cache flushes after kunmap/kunmap_atomic is called?
Date: Mon, 11 Aug 2008 16:19:03 -0700 [thread overview]
Message-ID: <48A0C8E7.6080506@cisco.com> (raw)
In-Reply-To: <1218206499.20791.152.camel@chaos.ne.broadcom.com>
Jon Fraser wrote:
> David,
>
> I'm battling this now. Our mips 24k has a virtually indexed cache.
> We're definitely seeing issues where the cache hasn't been flushed
> for highmem pages. I thought I had this fixed, but I'm still seeing
> some problems.
As I understand it, you have the most difficult combination of things:
o You are using high memory
o You have a virtually indexed cache
o You have data cache aliases
Fortunately, we have only the first two of those in our system. We should
probably put together a coherent set of patches for people who want high memory.
So far as I can tell, the 32-bit MIPS architecture has a long way to go before it
runs out of steam in the embedded world. I expect more people will need MIPS
highmem support in the next few years.
David
next prev parent reply other threads:[~2008-08-11 23:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 2:09 Anyone noticed that there are a lot of cache flushes after kunmap/kunmap_atomic is called? David VomLehn
2008-08-08 8:24 ` Ralf Baechle
2008-08-08 14:41 ` Jon Fraser
2008-08-11 23:19 ` David VomLehn [this message]
2008-08-12 0:49 ` Jon Fraser
2008-08-12 9:57 ` Kevin D. Kissell
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=48A0C8E7.6080506@cisco.com \
--to=dvomlehn@cisco.com \
--cc=jfraser@broadcom.com \
--cc=linux-mips@linux-mips.org \
--cc=michael.sundius@sciatl.com \
--cc=ralf@linux-mips.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