From: Robert Read <rread@datarithm.net>
To: Ishikawa <ishikawa@yk.rim.or.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel/printk.c: increasing the buffer size to capture devfsd debug messages.
Date: Tue, 20 Feb 2001 11:15:42 -0800 [thread overview]
Message-ID: <20010220111542.A4106@tenchi.datarithm.net> (raw)
In-Reply-To: <3A92A99E.2F255CB3@yk.rim.or.jp>
In-Reply-To: <3A92A99E.2F255CB3@yk.rim.or.jp>; from ishikawa@yk.rim.or.jp on Wed, Feb 21, 2001 at 02:30:08AM +0900
On Wed, Feb 21, 2001 at 02:30:08AM +0900, Ishikawa wrote:
>
> Has anyone tried 128K buffer size in kernel/printk.c
> and still have the kernel boot (without
> hard to notice memory corruption problems and other subtle bugs)?
> Any hints and tips will be appreciated.
I have used 128k and larger buffer sizes, and I just noticed this
fragment in the RedHat Tux Webserver patch. It creates a 2MB buffer:
--- linux/kernel/printk.c.orig Sun Jan 28 20:24:13 2001
+++ linux/kernel/printk.c Wed Jan 31 23:21:25 2001
@@ -22,7 +22,11 @@
#include <asm/uaccess.h>
-#define LOG_BUF_LEN (16384)
+#if CONFIG_TUX_DEBUG
+# define LOG_BUF_LEN (16384*128)
+#else
+# define LOG_BUF_LEN (16384)
+#endif
#define LOG_BUF_MASK (LOG_BUF_LEN-1)
static char buf[1024];
next prev parent reply other threads:[~2001-02-20 19:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-20 17:30 kernel/printk.c: increasing the buffer size to capture devfsd debug messages Ishikawa
2001-02-20 19:15 ` Robert Read [this message]
2001-02-20 19:37 ` Thomas Dodd
2001-02-20 20:17 ` [PATCH] " Robert Read
2001-02-20 20:53 ` Thomas Dodd
2001-02-20 21:03 ` Thomas Dodd
2001-02-20 22:05 ` Robert Read
2001-02-20 22:17 ` [PATCH] configurable printk buffer size Robert Read
2001-02-20 21:27 ` kernel/printk.c: increasing the buffer size to capture devfsd debug messages Ishikawa
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=20010220111542.A4106@tenchi.datarithm.net \
--to=rread@datarithm.net \
--cc=ishikawa@yk.rim.or.jp \
--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