public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jack Steiner <steiner@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 0/8] Optional ZONE_DMA V1
Date: Tue, 12 Sep 2006 13:34:57 +0000	[thread overview]
Message-ID: <20060912133457.GC10689@sgi.com> (raw)
In-Reply-To: <20060911222729.4849.69497.sendpatchset@schroedinger.engr.sgi.com>

On Mon, Sep 11, 2006 at 03:27:29PM -0700, Christoph Lameter wrote:
> Optional ZONE_DMA
> 
> This patch follows up on the earlier work in Andrew's tree to reduce
> the number of zones. The patches allow to go to a minimum of 2 zones.
> This one allows also to make ZONE_DMA optional and therefore the
> number of zones can be reduced to one.
> 
> ZONE_DMA is usually used for ISA DMA devices. Typically modern hardware
> does not have any of these anymore. So we frequently do not need
> the zone anymore. The presence of an additional zone unnecessarily
> complicates VM operations. It must be scanned and balancing logic
> must operate in it etc etc. If one has a 1-1 correspondence between
> zones and nodes in a NUMA system then various other optimizations
> become possible.
> 
> Many systems today (especially 64 bit but also 32 bit machines with less
> than 4G of memory) can therefore operate just fine with a single zone.
> With a single zone various loops can be optimized away by the
> compiler. Many system currently do not place anything in ZONE_DMA. On
> most of my systems ZONE_DMA is completely empty. Why constantly look
> at an empty zone in /proc/zoneinfo and empty slab in /proc/slabinfo?
> Non i386 also frequently have no need for ZONE_DMA and zones stay
> empty.
> 
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.

I assume your patch will switch Altix memory to a different zone, but what happens when
drivers specify GFP_DMA. 

-- jack

  parent reply	other threads:[~2006-09-12 13:34 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 [this message]
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=20060912133457.GC10689@sgi.com \
    --to=steiner@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