linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@sgi.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Jack Steiner <steiner@sgi.com>,
	Arjan van de Ven <arjan@infradead.org>,
	linux-mm@kvack.org, Nick Piggin <nickpiggin@yahoo.com.au>,
	Christoph Hellwig <hch@infradead.org>,
	linux-ia64@vger.kernel.org, Marcelo Tosatti <marcelo@kvack.org>,
	Martin Bligh <mbligh@google.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Andi Kleen <ak@suse.de>
Subject: Re: [PATCH 0/8] Optional ZONE_DMA V1
Date: Thu, 14 Sep 2006 10:52:43 +0200	[thread overview]
Message-ID: <4509185B.1020901@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0609131056260.18136@schroedinger.engr.sgi.com>

Christoph Lameter wrote:
> On Wed, 13 Sep 2006, Jack Steiner wrote:
> 
>> 	- will any IA64 platform require that ZONE_DMA be enabled (I think
>> 	  the answer is "yes")
> 
> I think that still remains to be discussed. Today there are various means
> to get around address restrictions.

I don't know about USB on ia64, but USB is an issue and we do support
it even on Altix, as crazy as it may seem (I use USB with my SGI Prism
foot-warmer in the office). Also take into account that some ia64 boxes
do not come with IOMMU's, DIG - be afraid, be very afraid. On those
machines you ideally want to have DMA32 zone for this stuff to support
32 bit PCI devices, even if the swiotlb can be used (bounce buffers for
all transactions is just a sick idea), and we get back to the issue of
using generic kernels.

>> 	- if ZONE_DMA is enabled, ALTIX will still use only 1 zone. In your
>> 	  statement above, you say that disabling ZONE_DMA save 1M cpu
>> 	  structures. If ZONE_DMA is enabled, will these 1M structure be allocated
>> 	  on SN even though they are not needed?
> 
> That has always been the case. In SLES9 and SLES10 we are using 1/4th of the pagesets.
> 
> Having no ZONE_DMA provides additional benefits besides saving memory. The 
> VM balancing of allocations within a node becomes not necessary and 
> various VM optimization can be performed. Loops are unrolled. Less zones 
> have to be processed for draining / vm counter updates etc etc.

I agree it sounds appealing, but if reality is that all distro kernels
will switch ZONE_DMA on, then having the option to switch it off is
going have little or zero impact on the end users.

In other words, will this really matter in end user situations?

Cheers,
Jes

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2006-09-14  8:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-18 18:36 [PATCH 0/8] Optional ZONE_DMA V2 Christoph Lameter
2006-09-18 18:36 ` [PATCH 1/8] Deal with cases of ZONE_DMA meaning the first zone Christoph Lameter
2006-09-18 18:36 ` [PATCH 2/8] Introduce CONFIG_ZONE_DMA Christoph Lameter
2006-09-18 18:36 ` [PATCH 3/8] Optional ZONE_DMA in the VM Christoph Lameter
2006-09-18 18:36 ` [PATCH 4/8] Optional ZONE_DMA for i386 Christoph Lameter
2006-09-18 18:36 ` [PATCH 5/8] Optional ZONE_DMA for x86_64 Christoph Lameter
2006-09-18 18:36 ` [PATCH 6/8] Optional ZONE_DMA for ia64 Christoph Lameter
2006-09-18 18:36 ` [PATCH 7/8] Remove ZONE_DMA remains from parisc Christoph Lameter
2006-09-18 18:36 ` [PATCH 8/8] Remove ZONE_DMA remains from sh/sh64 Christoph Lameter
     [not found]   ` <20060911222729.4849.69497.sendpatchset@schroedinger.engr.sgi.com>
     [not found]     ` <20060911222744.4849.26386.sendpatchset@schroedinger.engr.sgi.com>
     [not found]       ` <450600C7.7090801@yahoo.com.au>
2006-09-12  1:40         ` [PATCH 3/6] Optional ZONE_DMA in the VM Christoph Lameter
     [not found]     ` <20060912133457.GC10689@sgi.com>
     [not found]       ` <Pine.LNX.4.64.0609121032310.11278@schroedinger.engr.sgi.com>
2006-09-12 17:47         ` [PATCH 0/8] Optional ZONE_DMA V1 Martin Bligh
2006-09-12 17:53           ` Christoph Lameter
     [not found]     ` <1158046205.2992.1.camel@laptopd505.fenrus.org>
     [not found]       ` <Pine.LNX.4.64.0609121024290.11188@schroedinger.engr.sgi.com>
     [not found]         ` <yq0d5a0fbcj.fsf@jaguar.mkp.net>
     [not found]           ` <Pine.LNX.4.64.0609130109030.15792@schroedinger.engr.sgi.com>
     [not found]             ` <4507D4EE.4060501@sgi.com>
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 [this message]
2006-09-14 16:55                       ` Christoph Lameter
     [not found]     ` <20060911222739.4849.79915.sendpatchset@schroedinger.engr.sgi.com>
     [not found]       ` <20060918135559.GB15096@infradead.org>
     [not found]         ` <20060918152243.GA4320@localhost.na.rta>
2006-09-18 17:33           ` [PATCH 2/6] Introduce CONFIG_ZONE_DMA Christoph Lameter
2006-09-18 22:45             ` Paul Mundt
2006-09-18 22:58               ` Christoph Lameter
2006-09-18 23:25                 ` Paul Mundt
  -- strict thread matches above, loose matches on Subject: below --
2006-09-11 22:30 [PATCH 0/8] Optional ZONE_DMA V1 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=4509185B.1020901@sgi.com \
    --to=jes@sgi.com \
    --cc=ak@suse.de \
    --cc=arjan@infradead.org \
    --cc=clameter@sgi.com \
    --cc=hch@infradead.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=marcelo@kvack.org \
    --cc=mbligh@google.com \
    --cc=nickpiggin@yahoo.com.au \
    --cc=steiner@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox