From: Jes Sorensen <jes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 0/8] Optional ZONE_DMA V1
Date: Wed, 13 Sep 2006 07:55:01 +0000 [thread overview]
Message-ID: <yq0hczcfbfu.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <20060911222729.4849.69497.sendpatchset@schroedinger.engr.sgi.com>
>>>>> "Christoph" = Christoph Lameter <christoph@engr.sgi.com> writes:
Christoph> On Tue, 12 Sep 2006, Jack Steiner wrote:
>> I'm missing something here. On Altix, currently ALL of the memory
>> is reported as being in the DMA zone:
>>
>> % cat /proc/budd* Node 0, zone DMA 3015 116 4 1 ... Node 1, zone
>> DMA 4243 355 15 3 ... Node 2, zone DMA 4384 113 6 4 ...
>>
>> % cat /proc/zoneinfo Node 0, zone DMA pages free 5868 ...
>>
>> The DMA slabs are empty, though.
Christoph> This is wrong. All memory should be in ZONE_NORMAL since we
Christoph> have no DMA restrictions on Altix.
This is harmless on Altix because we have an IOMMU - however we should
in theory put all memory below 4GB into the DMA32 zone (if there was
any memory there :) to use if we ever ran out of IOMMU slots when
running 32 bit only capable PCI devices. I've never seen this happen
so it's purely theoretical.
Cheers,
Jes
next prev parent reply other threads:[~2006-09-13 7:55 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060918183614.19679.50359.sendpatchset@schroedinger.engr.sgi.com>
2006-09-11 22:27 ` [PATCH 0/8] Optional ZONE_DMA V1 Christoph Lameter
2006-09-11 22:27 ` [PATCH 2/6] Introduce CONFIG_ZONE_DMA Christoph Lameter
2006-09-18 13:55 ` Christoph Hellwig
2006-09-18 14:08 ` Martin Schwidefsky
2006-09-18 17:28 ` Christoph Lameter
2006-09-19 8:03 ` Martin Schwidefsky
2006-09-18 14:42 ` Russell King
2006-09-18 14:58 ` James Bottomley
2006-09-18 17:30 ` Christoph Lameter
2006-09-18 15:22 ` Paul Mundt
2006-09-18 17:33 ` Christoph Lameter
2006-09-18 22:45 ` Paul Mundt
2006-09-18 22:58 ` Christoph Lameter
2006-09-18 23:25 ` Paul Mundt
2006-09-11 22:27 ` [PATCH 3/6] Optional ZONE_DMA in the VM Christoph Lameter
2006-09-12 0:35 ` Nick Piggin
2006-09-12 1:40 ` Christoph Lameter
2006-09-12 2:40 ` Nick Piggin
2006-09-12 7:22 ` Andi Kleen
2006-09-12 8:30 ` Jes Sorensen
2006-09-12 9:12 ` Jes Sorensen
2006-09-12 18:05 ` Christoph Lameter
2006-09-12 7:30 ` [PATCH 0/8] Optional ZONE_DMA V1 Arjan van de Ven
2006-09-12 13:34 ` Jack Steiner
2006-09-12 17:25 ` Christoph Lameter
2006-09-12 17:33 ` Christoph Lameter
2006-09-12 17:47 ` Martin Bligh
2006-09-12 17:53 ` Christoph Lameter
2006-09-12 17:40 ` Martin Bligh
2006-09-13 2:41 ` Nick Piggin
2006-09-13 7:55 ` Jes Sorensen [this message]
2006-09-13 7:57 ` Jes Sorensen
2006-09-13 8:10 ` Christoph Lameter
2006-09-13 9:52 ` Jes Sorensen
2006-09-13 17:23 ` Christoph Lameter
2006-09-13 17:49 ` Jack Steiner
2006-09-13 18:00 ` Christoph Lameter
2006-09-14 8:52 ` Jes Sorensen
2006-09-14 16:55 ` Christoph Lameter
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=yq0hczcfbfu.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