From: Richard Henderson <rth@redhat.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Jens Axboe <axboe@suse.de>, Patrick Mochel <mochel@transmeta.com>,
Alan Cox <alan@redhat.com>, "David S. Miller" <davem@redhat.com>,
MOLNAR Ingo <mingo@chiara.elte.hu>,
Kanoj Sarcar <kanoj@google.engr.sgi.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] 32-bit dma memory zone
Date: Thu, 7 Jun 2001 14:59:12 -0700 [thread overview]
Message-ID: <20010607145912.B2286@redhat.com> (raw)
In-Reply-To: <20010607153119.H1522@suse.de> <Pine.LNX.4.21.0106071402480.6604-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.21.0106071402480.6604-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Thu, Jun 07, 2001 at 02:22:10PM -0700
On Thu, Jun 07, 2001 at 02:22:10PM -0700, Linus Torvalds wrote:
> For example, what's the difference between ZONE_HIGHMEM and ZONE_NORMAL
> on a sane 64-bit architecture (right now I _think_ the 64-bit architectures
> actually make ZONE_NORMAL be what we call ZONE_DMA32 on x86, because they
> already need to be able to distinguish between memory that can be PCI-DMA'd
> to, and memory that needs bounce-buffers. Or maybe it's ZONE_DMA that they
> use for the DMA32 stuff?).
On most alphas we use only one zone -- ZONE_DMA. The iommu makes it
possible to do 32-bit pci to the entire memory space.
For those alphas without an iommu, we also set up ZONE_NORMAL.
r~
next prev parent reply other threads:[~2001-06-07 21:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010607153119.H1522@suse.de>
2001-06-07 21:22 ` [patch] 32-bit dma memory zone Linus Torvalds
2001-06-07 21:59 ` Richard Henderson [this message]
2001-06-08 1:30 ` David S. Miller
2001-06-08 8:58 ` Steffen Persvold
2001-06-08 14:55 ` Eric W. Biederman
2001-06-08 21:00 ` H. Peter Anvin
2001-06-08 9:05 ` Russell King
2001-06-08 11:19 ` 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=20010607145912.B2286@redhat.com \
--to=rth@redhat.com \
--cc=alan@redhat.com \
--cc=axboe@suse.de \
--cc=davem@redhat.com \
--cc=kanoj@google.engr.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@chiara.elte.hu \
--cc=mochel@transmeta.com \
--cc=torvalds@transmeta.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.