public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jbarnes@sgi.com (Jesse Barnes)
To: Jes Sorensen <jes@trained-monkey.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [patch] 2.6.1-mm3 quiet down SMP boot messages
Date: Wed, 14 Jan 2004 10:20:52 -0800	[thread overview]
Message-ID: <20040114182052.GA8574@sgi.com> (raw)
In-Reply-To: <16389.21138.564775.207535@gargle.gargle.HOWL>

On Wed, Jan 14, 2004 at 09:30:42AM -0500, Jes Sorensen wrote:
> @@ -1118,6 +1117,7 @@
>  
>  	for(i = 0 ; i < numnodes ; i++)
>  		build_zonelists(NODE_DATA(i));
> +	printk("Built %i zonelists\n", numnodes);
>  }

How many of these for (i = 0; i < numnodes; i++) loops do we have?
Should we have a for_each_node() function like we do for CPUs?  Isn't
there a node_online() thing that many loops are missing?

Thanks,
Jesse

  reply	other threads:[~2004-01-14 18:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-14 14:30 [patch] 2.6.1-mm3 quiet down SMP boot messages Jes Sorensen
2004-01-14 18:20 ` Jesse Barnes [this message]
2004-01-15  2:02 ` Nick Piggin

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=20040114182052.GA8574@sgi.com \
    --to=jbarnes@sgi.com \
    --cc=akpm@osdl.org \
    --cc=jes@trained-monkey.org \
    --cc=linux-kernel@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