From: Roman Zippel <zippel@linux-m68k.org>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Tom Rini <trini@kernel.crashing.org>,
linux-kernel@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>,
szepe@pinerecords.com
Subject: Re: [PATCH] configurable LOG_BUF_SIZE
Date: Tue, 07 Jan 2003 01:12:04 +0100 [thread overview]
Message-ID: <3E1A1B54.A52307D2@linux-m68k.org> (raw)
In-Reply-To: Pine.LNX.4.33L2.0301061257160.15416-100000@dragon.pdx.osdl.net
Hi,
"Randy.Dunlap" wrote:
> +config LOG_BUF_SHIFT
> + int "Kernel log buffer size"
> + depends on DEBUG_KERNEL
Just change this into:
int "Kernel log buffer size" if DEBUG_KERNEL
> + default 17 if ARCH_S390
> + default 16 if X86_NUMAQ || IA64
> + default 15 if SMP
> + default 14
> + help
> + Select kernel log buffer size as a power of 2.
> + Defaults and Examples:
> + 17 (=> 128 KB for S/390)
> + 16 (=> 64 KB for x86 NUMAQ or IA-64)
> + 15 (=> 32 KB for SMP)
> + 14 (=> 16 KB for uniprocessor)
> + 13 (=> 8 KB)
> + 12 (=> 4 KB)
and you don't need this:
> +config LOG_BUF_SHIFT
> + int
> + depends on !DEBUG_KERNEL
> + default 17 if ARCH_S390
> + default 16 if X86_NUMAQ || IA64
> + default 15 if SMP
> + default 14
bye, Roman
prev parent reply other threads:[~2003-01-07 0:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 23:09 [PATCH] configurable LOG_BUF_SIZE Randy.Dunlap
2003-01-06 18:50 ` Tom Rini
2003-01-06 18:57 ` Randy.Dunlap
2003-01-06 19:06 ` Tom Rini
2003-01-06 19:05 ` Randy.Dunlap
2003-01-06 19:15 ` Tom Rini
2003-01-06 19:16 ` Linus Torvalds
2003-01-06 19:20 ` Randy.Dunlap
2003-01-06 21:06 ` Randy.Dunlap
2003-01-06 21:26 ` Tomas Szepe
2003-01-06 22:04 ` Randy.Dunlap
2003-01-06 22:56 ` Tom Rini
2003-01-06 23:30 ` [PATCH] configurable LOG_BUF_SIZE (updated) Randy.Dunlap
2003-01-06 23:57 ` Andrew Morton
2003-01-06 23:57 ` Randy.Dunlap
2003-01-07 0:12 ` Randy.Dunlap
2003-01-07 0:44 ` [PATCH] configurable LOG_BUF_SIZE (update-2) Randy.Dunlap
2003-01-07 0:12 ` Roman Zippel [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=3E1A1B54.A52307D2@linux-m68k.org \
--to=zippel@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=sam@ravnborg.org \
--cc=szepe@pinerecords.com \
--cc=torvalds@transmeta.com \
--cc=trini@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.