From: Dan Malek <dan@netx4.com>
To: Steve Rossi <srossi@ccrl.mot.com>
Cc: Embedded Linux PPC List <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: allocating non-cacheable regions
Date: Wed, 03 May 2000 15:52:44 -0400 [thread overview]
Message-ID: <3910838C.986942D6@embeddededge.com> (raw)
In-Reply-To: 39104A07.D997B6C5@ccrl.mot.com
Steve Rossi wrote:
>
> How do I allocate a region of memory that is flagged as being
> non-cacheable?
I am assuming you intend to do this on the 8xx processor as it
doesn't make sense on others. It may also not make sense on the 8xx
as it appears from testing that caching memory and push/invalidate
during I/O is better......
For an example, look at the commproc.c or enet.c driver in the
arch/ppc/8xx_io directory. When pages are allocated, the PTEs are
tracked down and marked non-cache.
> Does it have to be done at allocation or is it possible to mark a region
> non-cacheable
> after its been allocated?
I haven't found a way to get the kernel to allocate non-cache regions
of real memory. It would be nice if there was something along the
lines of DMA attribute, or perhaps I am just not looking in the right
place (and I am sure someone will point this out :-).
All I/O space is uncached and guarded.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-05-03 19:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-03 15:47 allocating non-cacheable regions Steve Rossi
2000-05-03 19:52 ` Dan Malek [this message]
2000-05-04 6:45 ` MPC860 enet driver dony
2000-05-31 20:53 ` allocating non-cacheable regions Steve Rossi
2000-05-31 22:12 ` Dan Malek
2000-05-31 22:39 ` Tom Roberts
2000-06-01 13:01 ` Steve Rossi
2000-06-01 20:10 ` Steve Rossi
2000-06-02 14:24 ` Steve Rossi
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=3910838C.986942D6@embeddededge.com \
--to=dan@netx4.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=srossi@ccrl.mot.com \
/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).