public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: IA64 without ZONE_DMA?
Date: Mon, 25 Sep 2006 19:17:20 +0000	[thread overview]
Message-ID: <yq0zmcnbvsv.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> On Sat, 23 Sep 2006, Jes Sorensen wrote:
>> 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.

Christoph> IA64 has no ZONE_DMA32. ZONE_DMA has a 4GB boundary for
Christoph> some architectures on IA64. The new page allocator call
Christoph> alloc_pages_range() would be able to allocate pages below
Christoph> the 4GB without having a ZONE_DMA (if necessary for 32 bit
Christoph> devices without proper IOMMU support).

I know the current code might not do whats really the right thing, but
I wanted to make sure we didn't prevent it in the future. If
alloc_pages_range() can do the job then that should be fine.

Cheers,
Jes

      parent reply	other threads:[~2006-09-25 19:17 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
2006-09-24  1:59 ` Christoph Lameter
2006-09-25 19:17 ` Jes Sorensen [this message]

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=yq0zmcnbvsv.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