From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Christoph Lameter <clameter@sgi.com>
Cc: Paul Mackerras <paulus@samba.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
jens.axboe@oracle.com
Subject: Re: Define CONFIG_BOUNCE to avoid useless inclusion of bounce buffer logic.
Date: Sun, 3 Jun 2007 23:24:39 +0100 [thread overview]
Message-ID: <20070603222439.GA16422@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0705232056400.24495@schroedinger.engr.sgi.com>
On Wed, May 23, 2007 at 09:03:02PM -0700, Christoph Lameter wrote:
> On Thu, 24 May 2007, Paul Mackerras wrote:
> > Also there is the problem that some drivers use ZONE_DMA allocations
> > because their device can only generate addresses below some limit, but
> > on a platform with an IOMMU there is in fact no restriction on what
> > memory the device can access.
>
> That problem is to some extend addressed by switching ZONE_DMA off which
> results in GFP_DMA becoming meaningless. And if GFP_DMA and ZONE_DMA is
> gone from a platform then the MAX_DMA_ADDRESS inconsistencies are solved
> since the cause of the inconsistencies has evaporated.
Suffice it to say then that with this approach ARM will _never_ be able
to have ZONE_DMA turned off, even on platforms where there are no DMA
restrictions. I guess that's something we'll just have to live with.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2007-06-03 22:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 4:03 Christoph Lameter
2007-05-22 4:39 ` KAMEZAWA Hiroyuki
2007-05-22 5:27 ` Christoph Lameter
2007-05-23 14:07 ` Russell King
2007-05-23 17:15 ` Christoph Lameter
2007-05-23 22:58 ` Russell King
2007-05-23 23:07 ` Christoph Lameter
2007-05-24 7:50 ` Russell King
2007-05-24 3:47 ` Paul Mackerras
2007-05-24 4:03 ` Christoph Lameter
2007-06-03 22:24 ` Russell King [this message]
2007-05-24 9:57 ` Alan Cox
2007-05-22 7:08 ` Jens Axboe
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=20070603222439.GA16422@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=jens.axboe@oracle.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.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
all inboxes | Powered by JetHome®