From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: "Sunil Naidu" <akula2.shark@gmail.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Frederik Deweerdt" <deweerdt@free.fr>,
"Andrew Morton" <akpm@linux-foundation.org>,
trivial@kernel.org
Subject: [PATCH] Move LOG_BUF_SHIFT to a more sensible place
Date: Fri, 27 Apr 2007 20:53:32 +0100 [thread overview]
Message-ID: <200704272053.32502.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <20070427085500.1c4b267c.randy.dunlap@oracle.com>
Several people have observed that perhaps LOG_BUF_SHIFT should be in a more
obvious place than under DEBUG_KERNEL. Under some circumstances (such as the
PARISC architecture), DEBUG_KERNEL can increase kernel size, which is an
undesirable trade off for something as trivial as increasing the kernel log
buffer size.
Instead, move LOG_BUF_SHIFT into "General Setup", so that people are more
likely to be able to change it such a circumstance that the default buffer
size is insufficient.
Signed-off-by: Alistair John Strachan <s0348365@sms.ed.ac.uk>
---
diff --git a/init/Kconfig b/init/Kconfig
index b170aa1..cc9eb35 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -262,6 +262,23 @@ config IKCONFIG_PROC
This option enables access to the kernel configuration file
through /proc/config.gz.
+config LOG_BUF_SHIFT
+ int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
+ range 12 21
+ default 17 if S390 || LOCKDEP
+ 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
+
config CPUSETS
bool "Cpuset support"
depends on SMP
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 3f3e740..de82401 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -86,23 +86,6 @@ config DEBUG_SHIRQ
Drivers ought to be able to handle interrupts coming in at those
points; some don't and need to be caught.
-config LOG_BUF_SHIFT
- int "Kernel log buffer size (16 => 64KB, 17 => 128KB)" if DEBUG_KERNEL
- range 12 21
- default 17 if S390 || LOCKDEP
- 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
-
config DETECT_SOFTLOCKUP
bool "Detect Soft Lockups"
depends on DEBUG_KERNEL && !S390
--
Cheers,
Alistair.
Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
next prev parent reply other threads:[~2007-04-27 19:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 12:14 Linux 2.6.21 - something wrong with dmesg Sunil Naidu
2007-04-26 13:03 ` Frederik Deweerdt
2007-04-26 14:35 ` Alistair John Strachan
2007-04-27 14:31 ` Sunil Naidu
2007-04-27 15:39 ` Alistair John Strachan
2007-04-27 15:55 ` Randy Dunlap
2007-04-27 19:53 ` Alistair John Strachan [this message]
2007-04-27 21:37 ` [PATCH] Move LOG_BUF_SHIFT to a more sensible place Randy Dunlap
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=200704272053.32502.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=akpm@linux-foundation.org \
--cc=akula2.shark@gmail.com \
--cc=deweerdt@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=trivial@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
all inboxes | Powered by JetHome®