From: David Mosberger <davidm@napali.hpl.hp.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Jes Sorensen <jes@wildopensource.com>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, David Mosberger <davidm@hpl.hp.com>,
jbarnes@sgi.com, Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [patch] quite down SMP boot messages
Date: Fri, 12 Dec 2003 14:27:12 -0800 [thread overview]
Message-ID: <16346.16576.987077.529284@napali.hpl.hp.com> (raw)
In-Reply-To: <20031212221609.GC314@elf.ucw.cz>
>>>>> On Fri, 12 Dec 2003 23:16:10 +0100, Pavel Machek <pavel@ucw.cz> said:
>> I'd like to propose this patch for 2.6.0 or 2.6.1 to quite down some
>> of the excessive boot messages printed for each CPU. The patch simply
>> introduces a boot time variable 'smpverbose' which users can set if
>> they experience problems and want to see the full set of messages.
>> Once you hit > 2 CPUs the amount of noise printed per CPU starts
>> becoming a pain, at 64 CPUs it's turning into a royal pain ....
Pavel> You might want to be more creative.. With something like < for each
Pavel> cpu going up and > for each cpu booted, you might be able to preserve
Pavel> all the info yet make it _way_ shorter.
Sounds promising to me. I also dislike the verbosity, but getting rid
of the messages completely makes me nervous, too, because sometimes
things do fail and then it's invaluable to have some idea of how far
the boot got (even if the person booting the machines has no clue what
the funny symbols on his screen actually mean).
--david
next prev parent reply other threads:[~2003-12-12 22:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 13:30 [patch] quite down SMP boot messages Jes Sorensen
2003-12-11 14:11 ` [patch] quiet " Jes Sorensen
2003-12-11 19:48 ` [patch] quite " Christoph Hellwig
2003-12-12 1:50 ` Rusty Russell
2003-12-12 8:46 ` Jes Sorensen
2003-12-12 22:16 ` Pavel Machek
2003-12-12 22:27 ` David Mosberger [this message]
2003-12-15 11:57 ` Jes Sorensen
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=16346.16576.987077.529284@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=akpm@osdl.org \
--cc=davidm@hpl.hp.com \
--cc=jbarnes@sgi.com \
--cc=jes@wildopensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rusty@rustcorp.com.au \
/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;
as well as URLs for NNTP newsgroup(s).