From: Robert Read <rread@datarithm.net>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] configurable printk buffer size
Date: Tue, 20 Feb 2001 14:17:42 -0800 [thread overview]
Message-ID: <20010220141742.D4106@tenchi.datarithm.net> (raw)
In-Reply-To: <3A92A99E.2F255CB3@yk.rim.or.jp> <20010220111542.A4106@tenchi.datarithm.net> <3A92C76C.6519DF1A@cypress.com> <20010220121727.B4106@tenchi.datarithm.net> <3A92D930.6F11B505@cypress.com> <20010220140515.C4106@tenchi.datarithm.net>
In-Reply-To: <20010220140515.C4106@tenchi.datarithm.net>; from rread@datarithm.net on Tue, Feb 20, 2001 at 02:05:15PM -0800
[-- Attachment #1: Type: text/plain, Size: 221 bytes --]
The obvious solution struck me just after the last email. I change
the config parameter to be an order, like the argument to
get_free_pages(). How does this look? It's not tested, but there
isn't much to it...
robert
[-- Attachment #2: printk-buflen.patch --]
[-- Type: text/plain, Size: 930 bytes --]
diff --exclude=*~ -ru linux-2.4.2-pre4/arch/i386/config.in linux-2.4.2-pre4-logbuf/arch/i386/config.in
--- linux-2.4.2-pre4/arch/i386/config.in Mon Jan 8 13:27:56 2001
+++ linux-2.4.2-pre4-logbuf/arch/i386/config.in Tue Feb 20 14:10:12 2001
@@ -366,4 +366,5 @@
#bool 'Debug kmalloc/kfree' CONFIG_DEBUG_MALLOC
bool 'Magic SysRq key' CONFIG_MAGIC_SYSRQ
+int 'Printk buffer size order 2**x' CONFIG_PRINTK_BUF_ORDER 14
endmenu
diff --exclude=*~ -ru linux-2.4.2-pre4/kernel/printk.c linux-2.4.2-pre4-logbuf/kernel/printk.c
--- linux-2.4.2-pre4/kernel/printk.c Tue Feb 20 11:56:31 2001
+++ linux-2.4.2-pre4-logbuf/kernel/printk.c Tue Feb 20 14:10:06 2001
@@ -23,7 +23,11 @@
#include <asm/uaccess.h>
-#define LOG_BUF_LEN (16384)
+#ifdef CONFIG_PRINTK_BUF_LEN
+# define LOG_BUF_LEN (2**CONFIG_PRINTK_BUF_ORDER)
+#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 22:18 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
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 ` Robert Read [this message]
2001-02-20 21:27 ` 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=20010220141742.D4106@tenchi.datarithm.net \
--to=rread@datarithm.net \
--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 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.