linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	akpm@linux-foundation.org, ak@suse.de, jbarnes@virtuousgeek.org
Subject: Re: [PATCH] change zonelist order v5 [1/3] implements zonelist order selection
Date: Tue, 08 May 2007 16:37:06 -0400	[thread overview]
Message-ID: <1178656627.5203.84.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.0705081104180.9941@schroedinger.engr.sgi.com>

On Tue, 2007-05-08 at 11:05 -0700, Christoph Lameter wrote:
> On Tue, 8 May 2007, Lee Schermerhorn wrote:
> 
> > > So far testing is IA64 only?
> > Yes, so far.  I will test on an Opteron platform this pm.  
> > Assume that no news is good news.
> 
> A better assumption: no news -> no testing. 

Before you asked, yes.  I meant after the last message, if you didn't
hear from me, everything worked fine.  And it does, sort of...


> You probably need a 
> configuration with a couple of nodes. Maybesomething less symmetric than 
> Kame? I.e. have 4GB nodes and then DMA32 takes out a sizeable chunk of it?
> 

I tested on a 2 socket, 4GB Opteron blade.  All memory is either DMA32
or DMA.  I added some ad hoc instrumentation to the build_zonelist_*
functions to see what's happening.  I have verified that the patches
appear to build the zonelists correctly:

default -> node order, because "low_kmem" [DMA+DMA32] > total_mem/2.
Zone lists:
DMA:  DMA-0
DMA32: DMA32-0, DMA-0, DMA32-1
Normal:  same as DMA32 [no normal memory]
Movable:  same as DMA32 & Normal

explicit zone order also builds as expected:
DMA:  DMA-0
DMA32:  DMA32-1, DMA32-0, DMA-0
and same for normal and movable

However, a curious thing happens:  in either order, allocations seem to
overflow to the remote DMA32 before dipping into the DMA!!!?  I'm using
memtoy to create a large [3+GB] anon segment and locking it down.

I need to check a non-patched kernel to see if it behaves the same way,
and examine the code to see why...  For one thing, the kernel seems to
do a bit better at reclaiming memory before overflowing.  Eventually, it
will dip into DMA and finally get killed--OOM.

I'll be off-line most of the rest of the week, so I probably won't get
to investigate much further nor test on a larger socket count/memory
system until next week.  

Lee



--
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:[~2007-05-08 20:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-08 11:14 [PATCH] change zonelist order v5 [0/3] KAMEZAWA Hiroyuki
2007-05-08 11:16 ` [PATCH] change zonelist order v5 [1/3] implements zonelist order selection KAMEZAWA Hiroyuki
2007-05-08 17:06   ` Lee Schermerhorn
2007-05-08 17:22     ` Christoph Lameter
2007-05-08 17:33       ` Lee Schermerhorn
2007-05-08 18:05         ` Christoph Lameter
2007-05-08 20:37           ` Lee Schermerhorn [this message]
2007-05-09  0:29             ` KAMEZAWA Hiroyuki
2007-05-09  0:58               ` Andrew Morton
2007-05-09  1:07                 ` Christoph Lameter
2007-05-09  1:20                 ` KAMEZAWA Hiroyuki
2007-05-09 13:55                   ` Lee Schermerhorn
2007-05-09  4:12                 ` KAMEZAWA Hiroyuki
2007-05-09  8:53                   ` Andy Whitcroft
2007-05-09  9:04                     ` KAMEZAWA Hiroyuki
2007-05-08 11:18 ` [PATCH] change zonelist order v5 [2/3] automatic configuration KAMEZAWA Hiroyuki
2007-05-08 17:07   ` Lee Schermerhorn
2007-05-08 11:19 ` [PATCH] change zonelist order v5 [3/3] documentation KAMEZAWA Hiroyuki
2007-05-08 17:08   ` Lee Schermerhorn
2007-05-09  0:23     ` KAMEZAWA Hiroyuki
2007-05-08 12:04 ` [PATCH] change zonelist order v5 [4/3] compile fix KAMEZAWA Hiroyuki
2007-05-08 16:14 ` [PATCH] change zonelist order v5 [0/3] 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=1178656627.5203.84.camel@localhost \
    --to=lee.schermerhorn@hp.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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