From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] patch to no longer use ia64's software mmu
Date: Tue, 04 Dec 2001 18:19:55 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805595@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805585@msgid-missing>
> Alan> I don't see the need: GFP_DMA is the ISA DMA zone. pci_* API
> Alan> is used by everyone else [for 2.5].
>
> Without a 4GB zone, you may end up creating bounce buffers needlessly
> for 32-bit capable DMA devices, no?
Yes - but it becomes an implementation detail. Drivers don't go around
asking for kmalloc in 4Gb zone anymore they ask for PCI memory that a 32bit
pci address can hit. I'm sure a 4Gb zone is what will be there internally
but you don't need GFP_4GBZONE as a visible driver detail.
Alan
next prev parent reply other threads:[~2001-12-04 18:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 21:00 [Linux-ia64] patch to no longer use ia64's software mmu Arjan van de Ven
2001-12-03 21:47 ` David Mosberger
2001-12-03 21:53 ` Arjan van de Ven
2001-12-04 18:14 ` David Mosberger
2001-12-04 18:19 ` Alan Cox [this message]
2001-12-04 19:55 ` David Mosberger
2001-12-04 19:56 ` David Mosberger
2001-12-04 19:56 ` David Mosberger
2001-12-04 20:22 ` David S. Miller
2001-12-04 20:32 ` David Mosberger
-- strict thread matches above, loose matches on Subject: below --
2001-12-03 21:00 Arjan van de Ven
2001-12-03 21:47 ` [Linux-ia64] " David Mosberger
2001-12-03 21:53 ` Arjan van de Ven
2001-12-04 9:36 ` Alan Cox
2001-12-04 16:26 ` David Mosberger
2001-12-04 16:32 ` Arjan van de Ven
2001-12-04 17:18 ` Alan Cox
2001-12-04 17:43 ` David Mosberger
2001-12-04 17:59 ` Alan Cox
2001-12-04 18:06 ` David Mosberger
2001-12-04 18:19 ` Alan Cox
2001-12-04 18:14 ` David Mosberger
2001-12-04 20:22 ` David S. Miller
2001-12-04 20:32 ` David Mosberger
2001-12-04 14:25 ` Andreas Schwab
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=marc-linux-ia64-105590698805595@msgid-missing \
--to=alan@lxorguk.ukuu.org.uk \
--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 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.