public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: "Dmitry A. Fedorov" <D.A.Fedorov@inp.nsk.su>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Proposal: Eliminate GFP_DMA
Date: Fri, 28 Feb 2003 16:05:50 +0000	[thread overview]
Message-ID: <20030228160550.B31251@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.SGI.4.10.10302282138180.244855-100000@Sky.inp.nsk.su>; from D.A.Fedorov@inp.nsk.su on Fri, Feb 28, 2003 at 09:44:14PM +0600

On Fri, Feb 28, 2003 at 09:44:14PM +0600, Dmitry A. Fedorov wrote:
> On 28 Feb 2003, Alan Cox wrote:
> > On Fri, 2003-02-28 at 14:12, Matthew Wilcox wrote:
> > > i'm not the kind of person who just changes the header file and breaks all
> > > the drivers.  plan:
> > > 
> > >  - Add the GFP_ATOMIC_DMA & GFP_KERNEL_DMA definitions
> > >  - Change the drivers
> > >  - Delete the GFP_DMA definition
> > 
> > Needless pain for people maintaining cross release drivers. Save it for
> > 2.7 where we should finally do the honourable deed given x86-64 may well
> > be mainstream, and simply remove GFP_DMA and expect people to use 
> > pci_*
> 
> But why drivers of ISA bus devices with DMA should use pci_* functions?
> 
> I'm personally wouldn't have too much pain with GFP_DMA because I have
> compatibility headers and proposed change for them is tiny.

Umm, question - I've seen ISA bridges with the ability to perform 32-bit
DMA using the ISA DMA controllers.  AFAIK, Linux doesn't make use of this
feature, except on ARM PCI systems with ISA bridges.  Is there a reason
why this isn't used on x86 hardware?

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  parent reply	other threads:[~2003-02-28 15:55 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
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 [this message]
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=20030228160550.B31251@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=D.A.Fedorov@inp.nsk.su \
    --cc=linux-kernel@vger.kernel.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