From: Dan Malek <dan@embeddededge.com>
To: Ronald Wahl <rwa@peppercon.de>
Cc: Benjamin Herrenschmidt <bh40@calva.net>, linuxppc-dev@lists.linuxppc.org
Subject: Re: allocating uncachable memory
Date: Fri, 25 Aug 2000 13:39:14 -0400 [thread overview]
Message-ID: <39A6AF42.323B88C@embeddededge.com> (raw)
In-Reply-To: Pine.LNX.4.21.0008250907160.1624-100000@goliath.issistance.de
Ronald Wahl wrote:
> After some further tests I found out that it is the data cache of the
> MPC860.
Yep.
> ..... So my
> question again: How can I get an alias mapping (with _PAGE_NO_CACHE |
> _PAGE_GUARDED) of some already mapped pages.
There isn't anything generic right now. A few of us are working on
a solution, as there are other processors affected (IBM 4xx) as well.
If you look at the uart or Ethernet drivers, you will notice they
allocate pages of memory, track down the PTEs and set the attributes
directly. You can use that as an example.
Don't forget that managing the caches in software (via flushes and
invalidates) could actually provide better performance for data
transfers due to the cache bursting available when caches are enabled.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-25 17:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-23 13:50 allocating uncachable memory Ronald Wahl
2000-08-23 14:03 ` Benjamin Herrenschmidt
2000-08-23 17:37 ` Dan Malek
2000-08-24 7:42 ` Ronald Wahl
2000-08-25 7:12 ` Ronald Wahl
2000-08-25 17:39 ` Dan Malek [this message]
2000-08-26 16:34 ` Roman Zippel
2000-08-27 19:46 ` Dan Malek
2000-08-27 21:26 ` Roman Zippel
2000-08-27 22:52 ` Dan Malek
2000-08-28 20:04 ` Roman Zippel
2000-08-28 20:34 ` Dan Malek
2000-08-28 21:33 ` Roman Zippel
2000-08-28 12:05 ` Ronald Wahl
2000-08-28 15:25 ` Dan Malek
2000-08-29 7:29 ` Ronald Wahl
2000-08-23 14:11 ` Gabriel Paubert
2000-08-24 9:14 ` Ronald Wahl
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=39A6AF42.323B88C@embeddededge.com \
--to=dan@embeddededge.com \
--cc=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=rwa@peppercon.de \
/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;
as well as URLs for NNTP newsgroup(s).