From: Andi Kleen <ak@suse.de>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: linux-scsi@vger.kernel.org, Christoph Lameter <clameter@sgi.com>
Subject: Re: GFP_DMA use in SCSI midlayer
Date: Sun, 1 Oct 2006 22:55:49 +0200 [thread overview]
Message-ID: <200610012255.49802.ak@suse.de> (raw)
In-Reply-To: <1159735218.3542.16.camel@mulgrave.il.steeleye.com>
On Sunday 01 October 2006 22:40, James Bottomley wrote:
> On Sun, 2006-10-01 at 22:13 +0200, Andi Kleen wrote:
> > GFP_DMA in general is deprecated and should be replaced by appropiate
> > dma_alloc_coherent()
>
> Um, no it shouldn't
>
> All of the places where we use GFP_DMA are because we might be
> addressing an ISA card or other strange mask limited card (gated usually
> by unchecked_isa_dma).
This means the majority of drivers will never use it? I don't
claim to be a SCSI expert, but a lot of uses looked unchecked
to me from a quick look. That is very worrying because it's
only 16MB on x86 and 16MB run out quickly.
If it's never used I don't care that much, but it certainly
doesn't look like that.
Or do you only need it because pci_map_single() on i386 doesn't
do bouncing? If yes we can probably fix that.
> However, what is wanted in every case is
> ordinary memory, not coherent memory. They can't simply be replaced
> with dma_alloc_coherent because
>
> a) it will waste memory for platforms that only do it in page size
> multiples
> b) It will fail on platforms that can't do it at all.
GFP_DMA will also fail on a lot of platforms, so it's the same.
> Coherent memory is really only for device drivers to use in mailboxes
> and shared ring buffers.
Maybe we need a new interface then with a mask. The plan is anyways
get rid of GFP_DMA completely because it has lots of problems. And
any user should declare the mask it really needs.
-Andi
next prev parent reply other threads:[~2006-10-01 20:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-01 20:13 GFP_DMA use in SCSI midlayer Andi Kleen
2006-10-01 20:40 ` James Bottomley
2006-10-01 20:55 ` Andi Kleen [this message]
2006-10-02 14:52 ` James Bottomley
2006-10-02 19:18 ` Andi Kleen
2006-10-02 22:24 ` Christoph Lameter
2006-10-02 18:43 ` Mike Christie
2006-10-02 18:51 ` Mike Christie
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=200610012255.49802.ak@suse.de \
--to=ak@suse.de \
--cc=James.Bottomley@steeleye.com \
--cc=clameter@sgi.com \
--cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.