From: Andi Kleen <ak@suse.de>
To: discuss@x86-64.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [discuss] Re: [1/3] Add 4GB DMA32 zone
Date: Mon, 12 Sep 2005 14:28:39 +0200 [thread overview]
Message-ID: <200509121428.40127.ak@suse.de> (raw)
In-Reply-To: <1126528473.30449.59.camel@localhost.localdomain>
On Monday 12 September 2005 14:34, Alan Cox wrote:
> On Llu, 2005-09-12 at 13:22 +0200, Andi Kleen wrote:
> > And with the mempool sleep approach they will just get small queues. Yes
> > that will be slower, but if you want performance on boxes with a lot of
> > memory you should not buy broken hardware.
>
> Ironically its broken hardware it works best with. AMD64 is problematic
> but Intel with the swiotlb works ;)
Actually the swiotlb code currently doesn't attempt to handle dma masks
<4GB even when the bounce pool happens to be located lower - it will just fail
or use GFP_DMA. It could be fixed in theory, but it would be pretty
unreliable and sometimes work on one system and sometimes not, so I would be
reluctant to go down that path.
Also BTW on many systems which don't allocate the IOMMU aperture in BIOS and
Linux has to allocate it over memory it tends to be as low (or high) as the
swiotlb pool - it is bootmem allocated at roughly the same place in boot.
But again the code doesn't attempt to handle that, it just uses hardcoded
0xffffffff masks.
-Andi
next prev parent reply other threads:[~2005-09-12 12:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-11 16:59 [1/3] Add 4GB DMA32 zone Andi Kleen
2005-09-12 7:44 ` [discuss] " Jan Beulich
2005-09-12 7:58 ` Andi Kleen
2005-09-12 10:28 ` Alan Cox
2005-09-12 10:42 ` Andi Kleen
2005-09-12 11:33 ` Alan Cox
2005-09-12 11:22 ` Andi Kleen
2005-09-12 12:34 ` Alan Cox
2005-09-12 12:28 ` Andi Kleen [this message]
2005-09-12 18:18 ` Jeff Garzik
2005-09-12 22:02 ` Bart Hartgers
2005-09-13 3:20 ` Andi Kleen
2005-09-12 19:55 ` Mark Lord
2005-09-12 12:45 ` Roman Zippel
2005-09-12 12:46 ` Andi Kleen
2005-09-12 12:50 ` Roman Zippel
2005-09-12 12:54 ` Andi Kleen
2005-09-12 13:01 ` Roman Zippel
2005-09-13 9:15 ` Roman Zippel
2005-09-13 9:47 ` [discuss] " Andi Kleen
2005-09-13 10:15 ` Andrew Morton
2005-09-13 11:32 ` Andi Kleen
2005-09-13 12:09 ` Roman Zippel
2005-09-13 23:51 ` KAMEZAWA Hiroyuki
2005-10-03 15:46 ` Coywolf Qi Hunt
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=200509121428.40127.ak@suse.de \
--to=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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