lkml.org 
[lkml]   [2001]   [Feb]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
Date
From
SubjectRe: kernel/printk.c: increasing the buffer size to capture devfsd debug messages.
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];
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:17    [W:0.054 / U:0.040 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site