linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Andi Kleen <ak@muc.de>, linux-mm@kvack.org, akpm@digeo.com
Subject: Re: Redundant zonelist initialization
Date: Thu, 8 May 2003 16:52:18 +0200	[thread overview]
Message-ID: <20030508145218.GA4355@averell> (raw)
In-Reply-To: <24990000.1052396565@[10.10.2.4]>

On Thu, May 08, 2003 at 02:22:47PM +0200, Martin J. Bligh wrote:
> 
> 
> --On Thursday, May 08, 2003 13:23:39 +0200 Andi Kleen <ak@muc.de> wrote:
> 
> > When booting 2.5.69 on a 4 Node CONFIG_DISCONTIGMEM machine I get:
> > 
> > Building zonelist for node : 0
> > Building zonelist for node : 1
> > Building zonelist for node : 2
> > Building zonelist for node : 3
> > Building zonelist for node : 0
> > Building zonelist for node : 0
> > Building zonelist for node : 0
> > Building zonelist for node : 0
> > 
> > Why does it initialize the zonelist for node 0 five times?
> 
> Looks like you have numnodes wrong ...
> 
> void __init build_all_zonelists(void)
> {
>         int i;
> 
>         for(i = 0 ; i < numnodes ; i++)
>                 build_zonelists(NODE_DATA(i));
> }

Only with new mathematics :-) How can any value for numnodes explain 
such a sequence ? 

I think it actually comes from the two loops calling build_zonelist_node 
in build_zonelists(). But I'm not sure why it produces such a strange sequence.

-Andi
--
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:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2003-05-08 14:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-08 11:23 Andi Kleen
2003-05-08 12:22 ` Martin J. Bligh
2003-05-08 14:52   ` Andi Kleen [this message]
2003-05-08 22:41     ` Martin J. Bligh

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=20030508145218.GA4355@averell \
    --to=ak@muc.de \
    --cc=akpm@digeo.com \
    --cc=linux-mm@kvack.org \
    --cc=mbligh@aracnet.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