From: Nick Piggin <nickpiggin@yahoo.com.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 3/6] Optional ZONE_DMA in the VM
Date: Tue, 12 Sep 2006 00:35:19 +0000 [thread overview]
Message-ID: <450600C7.7090801@yahoo.com.au> (raw)
In-Reply-To: <20060911222744.4849.26386.sendpatchset@schroedinger.engr.sgi.com>
Christoph Lameter wrote:
> Make ZONE_DMA optional in core code.
>
> - ifdef definitions for ZONE_DMA and related code following
> the example for ZONE_DMA32 and ZONE_HIGHMEM.
>
> - Without ZONE_DMA, ZONE_HIGHMEM and ZONE_DMA32 we get to a
> ZONES_SHIFT of 0.
>
> - Modify the VM statistics to work correctly without a DMA
> zone.
>
> - Modify slab to not create DMA slabs if there is no
> ZONE_DMA.
>
> Signed-off-by: Christoph Lameter <clameter@sgi.com>
Nice. Looks like it should remove a bit of overhead.
I can't see from your patches, but what happens if someone asks
for a GFP_DMA page or dma slab allocation when there is no ZONE_DMA?
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2006-09-12 0:35 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 [this message]
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
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=450600C7.7090801@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--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