From: Dan Malek <dan@netx4.com>
To: Roman Zippel <zippel@fh-brandenburg.de>
Cc: Dan Malek <dan@netx4.com>, Ronald Wahl <rwa@peppercon.de>,
Benjamin Herrenschmidt <bh40@calva.net>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: allocating uncachable memory
Date: Sun, 27 Aug 2000 18:52:05 -0400 [thread overview]
Message-ID: <39A99B95.6F0109D8@embeddededge.com> (raw)
In-Reply-To: Pine.GSO.4.10.10008272258170.29427-100000@zeus.fh-brandenburg.de
Roman Zippel wrote:
> If you mark the page(s) as reserved it should already do the right thing
> on most architectures. The only problem is ioremap doesn't take an array
> of pages.
Hmmm...I thought reserved didn't imply that much information. The 8xx
allocates some memory early to get is reserved, but you still have to
perform the PTE updates to get the cache attributes.
> Another possibility is __vmalloc(), that already has a protection
> argument and you only need a virt_to_xxx() to get the address of the
> allocated pages.
That's the current plan. If all you need is virt_to_xxx() it's easy.
The xxx_to_virt() is nearly impossible. I have a VM implementation that
uses (or tries to) mixed large pages, but all of the existing assumptions
about memory mapping fail. Everything will have to vmalloc() and then
use virt_to_xxx/xxx_to_virt() (which are much more than simple addition
macros). I'm waiting for some of the PCI mapping discussions to make
sufficient changes to the I/O subsystem so I can just use those.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-27 22:52 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
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 [this message]
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=39A99B95.6F0109D8@embeddededge.com \
--to=dan@netx4.com \
--cc=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=rwa@peppercon.de \
--cc=zippel@fh-brandenburg.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).