From: Russell King <rmk@arm.linux.org.uk>
To: Eli Carter <eli.carter@inet.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
Jeff Garzik <jgarzik@pobox.com>, Andi Kleen <ak@suse.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Matthew Wilcox <willy@debian.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Proposal: Eliminate GFP_DMA
Date: Fri, 28 Feb 2003 16:03:37 +0000 [thread overview]
Message-ID: <20030228160337.A31251@flint.arm.linux.org.uk> (raw)
In-Reply-To: <3E5F84FE.1050409@inet.com>; from eli.carter@inet.com on Fri, Feb 28, 2003 at 09:49:18AM -0600
On Fri, Feb 28, 2003 at 09:49:18AM -0600, Eli Carter wrote:
> To do it properly, I think you'd need to give a range, not just an upper
> bound. On some ARM / XScale systems, you can specify a window of your
> RAM that is visible on the PCI bus. That may be a case too odd to care
> about, but I'm going to have to at some point in the future....
Which may not start at address zero either.
There are even ARM systems where it'd be useful to be able to say "only
allocate memory in region N where N = first 1MB of every 2MB region.
(Yes, I know, this broken hardware should die, but it just isn't going
away thanks to the marketing powers of large IC manufacturers.)
Maybe the generic solution could be something like the resource allocation
functions which are passed an alignment function? /me hides.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-02-28 15:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030228064631.G23865@parcelfarce.linux.theplanet.co.uk.suse.lists.linux.kernel>
2003-02-28 8:56 ` Proposal: Eliminate GFP_DMA Andi Kleen
2003-02-28 14:12 ` Matthew Wilcox
2003-02-28 15:24 ` Alan Cox
2003-02-28 14:34 ` Matthew Wilcox
2003-02-28 15:55 ` Alan Cox
2003-02-28 14:56 ` Andi Kleen
2003-02-28 15:25 ` Jeff Garzik
2003-02-28 15:30 ` Andi Kleen
2003-02-28 15:34 ` Martin J. Bligh
2003-02-28 15:49 ` Eli Carter
2003-02-28 16:03 ` Russell King [this message]
2003-02-28 16:45 ` Alan Cox
2003-02-28 15:31 ` Arjan van de Ven
2003-03-04 17:56 ` Rogier Wolff
2003-03-04 23:09 ` Alan Cox
2003-03-05 7:43 ` Rogier Wolff
2003-03-05 13:53 ` Alan Cox
2003-02-28 15:44 ` Dmitry A. Fedorov
2003-02-28 15:58 ` Jeff Garzik
2003-02-28 18:17 ` Deepak Saxena
2003-02-28 18:27 ` Deepak Saxena
2003-02-28 19:52 ` Russell King
[not found] ` <mailman.1046456425.7772.linux-kernel2news@redhat.com>
2003-02-28 20:51 ` Pete Zaitcev
2003-02-28 22:11 ` Russell King
2003-02-28 16:05 ` Russell King
2003-02-28 17:27 ` Ivan Kokshaysky
2003-02-28 17:45 ` Alan Cox
2003-02-28 6:46 Matthew Wilcox
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=20030228160337.A31251@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=eli.carter@inet.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=willy@debian.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