From: Jeff Garzik <jgarzik@pobox.com>
To: Andi Kleen <ak@suse.de>
Cc: 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 10:25:02 -0500 [thread overview]
Message-ID: <20030228152502.GA32449@gtf.org> (raw)
In-Reply-To: <20030228145614.GA27798@wotan.suse.de>
On Fri, Feb 28, 2003 at 03:56:15PM +0100, Andi Kleen wrote:
> On Fri, Feb 28, 2003 at 03:55:37PM +0000, Alan Cox wrote:
> > On Fri, 2003-02-28 at 14:34, Matthew Wilcox wrote:
> > > umm. are you volunteering to convert drivers/net/macmace.c to the pci_*
> > > API then? also, GFP_DMA is used on, eg, s390 to get memory below 2GB and
> > > on ia64 to get memory below 4GB.
> >
> > The ia64 is a fine example of how broken it is. People have to hack around
> > with GFP_DMA meaning different things on ia64 to everything else. It needs
> > to die.
>
> At least on x86-64 it is still needed when you need have some hardware
> with address limits < 4GB (e.g. an 24bit soundcard)
>
> pci_* on K8 only allows address mask 0xffffffff or unlimited.
That's a bit broken... I have an ALS4000 PCI soundcard that is a 24-bit
soundcard. pci_set_dma_mask should support 24-bits accordingly,
otherwise it's a bug in your platform implementation... Nobody will be
able to use certain properly-written drivers on your platform otherwise.
Jeff
next prev parent reply other threads:[~2003-02-28 15:14 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 [this message]
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
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=20030228152502.GA32449@gtf.org \
--to=jgarzik@pobox.com \
--cc=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--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