From: James Bottomley <James.Bottomley@SteelEye.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>,
Aubrey Li <aubreylee@gmail.com>,
Christoph Lameter <clameter@sgi.com>,
Bernhard Walle <bwalle@suse.de>,
linux-scsi@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [scsi] Remove __GFP_DMA
Date: Sun, 27 May 2007 14:46:39 -0500 [thread overview]
Message-ID: <1180295199.3711.24.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <20070523203846.41ac5011@the-village.bc.nu>
On Wed, 2007-05-23 at 20:38 +0100, Alan Cox wrote:
> On Wed, 23 May 2007 15:17:08 -0400
> "Salyzyn, Mark" <mark_salyzyn@adaptec.com> wrote:
>
> > The 31 bit limit for some of these cards is a problem, we currently only
> > do __GFP_DMA for bounce buffer sg elements allocated for user supplied
> > references in ioctls.
> >
> > I figure we should be using pci_alloc_consistent calls for these
> > allocations to more accurately acquire memory within the 31 bit limit if
> > necessary, we could switch to these to remove the need for the __GFP_DMA
> > flag in the aacraid driver?
>
> That didn't used to work right on the AMD boards when I tried it last as
> we ended up with a buffer that was mapped by the IOMMU for some reason
> and that was not below 2GB.
Is that a bug in the x86_64 subsystem ... or just a bug in the HW?
I'm assuming what happened is that the GART aperture was placed above
the 2GB limit making the GART unable to act as an IOMMU for any devices
with a dma_mask < 32bit?
This does show up a problem in our dma_ functions: namely that if the
system says it has an IOMMU then we assume it's fully functional (i.e.
able to reach all addresses). There was a move afoot a while ago to
replace the single PCI_DMA_BUS_IS_PHYS macro which is used to tell the
system globally if we have an IOMMU with something like
dma_dev_uses_iommu(struct device *) which would do the same thing but on
a per-device basis. Does this need to be resurrected?
James
next prev parent reply other threads:[~2007-05-27 19:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 15:15 Bernhard Walle
2007-05-22 21:44 ` Christoph Lameter
2007-05-23 2:41 ` Aubrey Li
2007-05-23 15:18 ` James Bottomley
2007-05-23 15:55 ` Robert P. J. Day
2007-05-23 16:17 ` James Bottomley
2007-05-23 19:17 ` Salyzyn, Mark
2007-05-23 19:38 ` Alan Cox
2007-05-27 19:46 ` James Bottomley [this message]
2007-05-24 13:24 ` Salyzyn, Mark
2007-05-24 14:59 ` James Bottomley
2007-05-24 17:00 ` Christoph Lameter
2007-05-24 17:15 ` James Bottomley
2007-05-24 17:22 ` Christoph Lameter
2007-05-24 17:26 ` James Bottomley
2007-05-24 16:59 ` Christoph Lameter
[not found] <fa.6bUV4KR+za7HW4tT2WBlccqvoq0@ifi.uio.no>
[not found] ` <fa.NYl60pD1cwd1ESdKNCPaOwSz1WA@ifi.uio.no>
[not found] ` <fa.hW9tQQfgwmXj0gAKQoWXOxVzpvk@ifi.uio.no>
[not found] ` <fa.xLFpJ54sTvGq6YIol2Ew31Rrq2s@ifi.uio.no>
[not found] ` <fa.JZsPKKyEKOAfxp6reMY5ZwSNjQU@ifi.uio.no>
[not found] ` <fa.txrEcCPLxIukzeVBv7UG39WubcI@ifi.uio.no>
2007-05-24 5:28 ` Robert Hancock
2007-05-24 10:08 ` Alan Cox
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=1180295199.3711.24.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=aubreylee@gmail.com \
--cc=bwalle@suse.de \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.com \
/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
all inboxes | Powered by JetHome®