From: Artem Bityutskiy <dedekind@infradead.org>
To: linux-kernel@vger.kernel.org
Subject: [RFC] [PATCH] Kconfig: enlarge printk buffer size limit
Date: Fri, 02 Mar 2007 15:27:48 +0200 [thread overview]
Message-ID: <1172842068.17031.55.camel@sauron> (raw)
From: Artem Bityutskiy <artem.bityutskiy@nokia.com>
Subject: [RFC] [PATCH] Kconfig: enlarge printk buffer size limit
This patch makes the upper kernel ring buffer size limit larger. It
is often very handy to have huge ring-buffer for debugging purposes,
when the subsystem which is being debugged produces large amount of
useful output.
Index: ubi-2.6.git/lib/Kconfig.debug
===================================================================
--- ubi-2.6.git.orig/lib/Kconfig.debug
+++ ubi-2.6.git/lib/Kconfig.debug
@@ -79,7 +79,7 @@ config DEBUG_KERNEL
config LOG_BUF_SHIFT
int "Kernel log buffer size (16 => 64KB, 17 => 128KB)" if DEBUG_KERNEL
- range 12 21
+ range 12 26
default 17 if S390 || LOCKDEP
default 16 if X86_NUMAQ || IA64
default 15 if SMP
next reply other threads:[~2007-03-02 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 13:27 Artem Bityutskiy [this message]
2007-03-02 17:11 ` [RFC] [PATCH] Kconfig: enlarge printk buffer size limit Randy Dunlap
2007-03-07 11:33 ` Artem Bityutskiy
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=1172842068.17031.55.camel@sauron \
--to=dedekind@infradead.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