From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: Linus Torvalds <torvalds@transmeta.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] making the printk buffer bigger
Date: Mon, 29 Oct 2001 16:25:19 -0800 [thread overview]
Message-ID: <3645339074.1004372719@mbligh.des.sequent.com> (raw)
In-Reply-To: <3040507575.1003767887@mbligh.des.sequent.com>
> For larger machines, 16K isn't big enough to hold all the boot
> messages - which means some of the earlier boot messages don't
> make it to the log files.
>
> Could you add this tiny patch to fix it?
OK, seeing as people don't seem to want a decent size buffer on
CONFIG_SMP machines, could we at least do it under
CONFIG_MULTIQUAD? Loosing half my boot time messages is
annoying, and I have gigabytes of RAM to waste. Please .......
M.
diff -urN virgin-2.4.13-pre2/kernel/printk.c linux-2.4.13-pre2/kernel/printk.c
--- virgin-2.4.13-pre2/kernel/printk.c Mon Sep 17 13:16:30 2001
+++ linux-2.4.13-pre2/kernel/printk.c Mon Oct 15 13:15:37 2001
@@ -27,7 +27,12 @@
#include <asm/uaccess.h>
-#define LOG_BUF_LEN (16384) /* This must be a power of two */
+#ifdef CONFIG_MULTIQUAD
+#define LOG_BUF_LEN (65536) /* This must be a power of two */
+#else
+#define LOG_BUF_LEN (16384) /* This must be a power of two */
+#endif
+
#define LOG_BUF_MASK (LOG_BUF_LEN-1)
/* printk's without a loglevel use this.. */
next prev parent reply other threads:[~2001-10-30 0:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-22 23:24 Martin J. Bligh
2001-10-30 0:25 ` Martin J. Bligh [this message]
2001-10-30 13:14 ` Maciej W. Rozycki
2001-10-30 18:19 ` Martin J. Bligh
2001-10-31 11:31 ` Maciej W. Rozycki
2001-10-31 17:03 ` Martin J. Bligh
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=3645339074.1004372719@mbligh.des.sequent.com \
--to=martin.bligh@us.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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®