From: Ralf Baechle <ralf@linux-mips.org>
To: Jimmy Zhang <jzhang@elmic.com>
Cc: linux-mips@linux-mips.org
Subject: Re: How to make part of kseg0 uncached
Date: Sat, 3 May 2003 03:06:58 +0200 [thread overview]
Message-ID: <20030503030657.A1756@linux-mips.org> (raw)
In-Reply-To: <004f01c31106$7cb63de0$0300a8c0@riverside>; from jzhang@elmic.com on Fri, May 02, 2003 at 04:56:44PM -0700
On Fri, May 02, 2003 at 04:56:44PM -0700, Jimmy Zhang wrote:
> It is pretty simple to make the WHOLE kseg0 cached or uncached. However,
> I only want part of kseg0 uncached.
>
> I must uncache that region because it gives me too much trouble with DMA
> data, however, I don't want to uncache the whole kseg0 segment in order
> to get better performance. Kseg0 is not mapped through TLB, so it seems
> I can't achieve my goal through TLB.
>
> Cite from the book See Mips Run, "if you feel that your system needs to
> make uncached references to cacheable memory, then I strongly recommand
> that you divide memory into regions that are always accessed uncached
> and regions that are always accessed through the cache - and don't let
> them overlap. " But how ?
By not using KSEG0 for all your data. As you figured the caching mode only
can only modifed for the entire KSEG0. And because some part of your
code such as exception handlers will always run in KSEG0 you never want
to switch KSEG0 to uncached. Easy solution, KSEG1 maps the same address
space as KSEG0 but is always uncached. The usual warning applies, using
uncached memory is a bad idea in most cases.
Ralf
prev parent reply other threads:[~2003-05-03 1:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-02 23:56 How to make part of kseg0 uncached Jimmy Zhang
2003-05-02 23:56 ` Jimmy Zhang
2003-05-03 1:06 ` Ralf Baechle [this message]
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=20030503030657.A1756@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=jzhang@elmic.com \
--cc=linux-mips@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