public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: Jes Sorensen <jes@trained-monkey.org>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, Jesse Barnes <jbarnes@sgi.com>
Subject: Re: [patch] 2.6.1-mm3 quiet down SMP boot messages
Date: Thu, 15 Jan 2004 13:02:52 +1100	[thread overview]
Message-ID: <4005F4CC.2070104@cyberone.com.au> (raw)
In-Reply-To: <16389.21138.564775.207535@gargle.gargle.HOWL>



Jes Sorensen wrote:

>Hi,
>
>I'd like to propose the following for 2.6.1-mm/2.6.2. On systems with a
>large number of CPUs the number of printk's flowing by for each CPU
>booting starts becoming a real console hog.
>
>The following patch eliminates a couple of them (already sent a patch to
>David for the ia64 specific ones) as well as changes the 
>"Building zonelist : X" in "Built Y zonelists". IMHO it doesn't make any
>sense to print for each zonelist since it's run in a for loop running
>from 0 to Y-1 anyway.
>
>The patch nukes a few new printk's that were introduced with the
>scheduler changes to the NUMA code in -mm3, if these are still needed
>then I won't fight for that part of the patch.
>

Thanks, I forgot to remove those printks because I don't have a NUMA
handy I guess. They're just to make sure the sched domains where being
initialized properly. They can go.

I like the rest of the patch too.



      parent reply	other threads:[~2004-01-15  2:07 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
2004-01-15  2:02 ` Nick Piggin [this message]

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=4005F4CC.2070104@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=akpm@osdl.org \
    --cc=jbarnes@sgi.com \
    --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