From: Tejun Heo <tj@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Mike Travis <travis@sgi.com>, "H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Rientjes <rientjes@google.com>, Len Brown <lenb@kernel.org>,
Jack Steiner <steiner@sgi.com>, Lori Gilbertson <loriann@sgi.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Early kernel messages are overflowing the static log buffer
Date: Wed, 22 Dec 2010 14:17:19 +0100 [thread overview]
Message-ID: <20101222131719.GA8061@htj.dyndns.org> (raw)
In-Reply-To: <20101222130946.GC13412@elte.hu>
Hello,
On Wed, Dec 22, 2010 at 02:09:46PM +0100, Ingo Molnar wrote:
> > [ 0.000000] pcpu-alloc: [000] 0000 0001 0002 0003 0004 0005 0006 0007 1024 1025 1026 1027 1028 1029 1030 1031
> >
> > What I'm asking is which of these would be most acceptable to
> > either remove or replace with some sort of message reduction?
>
> The pcpu alloc messages look entirely superfluous and zappable - make them
> KERN_DEBUG perhaps (and Cc: Tejun)?
Yeap, with percpu allocator now mostly stable, I don't think the
message needs to be KERN_INFO anymore. I'll change it to KERN_DEBUG.
Thanks.
--
tejun
next prev parent reply other threads:[~2010-12-22 13:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 23:58 Early kernel messages are overflowing the static log buffer Mike Travis
2010-12-22 13:09 ` Ingo Molnar
2010-12-22 13:17 ` Tejun Heo [this message]
2010-12-22 13:22 ` [PATCH] percpu: print out alloc information with KERN_DEBUG instead of KERN_INFO Tejun Heo
2010-12-22 18:56 ` Early kernel messages are overflowing the static log buffer Mike Travis
2010-12-22 19:03 ` Mike Travis
2010-12-22 21:21 ` Ingo Molnar
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=20101222131719.GA8061@htj.dyndns.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loriann@sgi.com \
--cc=mingo@elte.hu \
--cc=rientjes@google.com \
--cc=steiner@sgi.com \
--cc=travis@sgi.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