From: Jes Sorensen <jes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: IA64 without ZONE_DMA?
Date: Sat, 23 Sep 2006 20:05:33 +0000 [thread overview]
Message-ID: <yq08xkacprm.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0609221622170.10232@schroedinger.engr.sgi.com>
>>>>> "Christoph" = Christoph Lameter <clameter@sgi.com> writes:
Christoph> There is code in Andrews tree that allows getting rid of
Christoph> ZONE_DMA. I know that SGI machines do not use ZONE_DMA. I
Christoph> looked through the arch code and I do not see ZONE_DMA or
Christoph> GFP_DMA uses that I cannot account for. However, I am not
Christoph> familiar with the code for other IA64 platforms.
Christoph> This patch will make IA64 have a single zone in each
Christoph> node. As a result loops are unrolled, various VM macros can
Christoph> be optimized further and the memory load balancing code
Christoph> between different zones in one node is no longer
Christoph> necessary. Note that having no ZONE_DMA means that GFP_DMA
Christoph> will be ignored. If you know of any devices depending on
Christoph> ZONE_DMA (memory returned must be below 4GB) then we first
Christoph> need to deal with those possibly by modifying
Christoph> dma_alloc_coherent functions to obtain memory in a
Christoph> different way than via GFP_DMA.
If you want to take this path, are you then planning to move the < 4GB
memory into ZONE_DMA32? We need a way to allocate memory within the
4GB zone for 32 bit DMA devices, especially on systems without an
IOMMU. In fact, it's attractive to be able to get memory in the 4GB
zone when possible even if a device supports DAC as it reduces the
number of bus transactions since it can be done with a single address
cycle instead of a dual.
Jes
next prev parent reply other threads:[~2006-09-23 20:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 23:30 IA64 without ZONE_DMA? Christoph Lameter
2006-09-23 1:18 ` KAMEZAWA Hiroyuki
2006-09-23 1:38 ` Christoph Lameter
2006-09-23 20:05 ` Jes Sorensen [this message]
2006-09-24 1:59 ` Christoph Lameter
2006-09-25 19:17 ` Jes Sorensen
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=yq08xkacprm.fsf@jaguar.mkp.net \
--to=jes@sgi.com \
--cc=linux-ia64@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