linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ford <david@linux.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH/REQ] Increase kmsg buffer from 16K to 32K, kernel/printk.c
Date: Sat, 27 Jan 2001 08:01:14 +0000	[thread overview]
Message-ID: <3A72804A.E6052E1B@linux.com> (raw)

Does Linus or anyone object to raising the ksmg buffer from 16K to 32K?
4/5 systems I have now overflow the buffer during boot before init is
even launched.

--- linux/kernel/printk.c~    Fri Jan 26 18:50:28 2001
+++ linux/kernel/printk.c     Fri Jan 26 23:59:31 2001
@@ -22,7 +22,7 @@

 #include <asm/uaccess.h>

-#define LOG_BUF_LEN    (16384)
+#define LOG_BUF_LEN    (32768)
 #define LOG_BUF_MASK   (LOG_BUF_LEN-1)

 static char buf[1024];

-d

--
  There is a natural aristocracy among men. The grounds of this are virtue and talents. Thomas Jefferson
  The good thing about standards is that there are so many to choose from. Andrew S. Tanenbaum



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2001-01-27  8:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-27  8:01 David Ford [this message]
2001-01-31 17:06 ` [PATCH/REQ] Increase kmsg buffer from 16K to 32K, kernel/printk.c Alan Cox
2001-01-31 17:19   ` Maciej W. Rozycki
2001-01-31 23:12     ` David Ford
2001-01-31 17:21   ` Gabor Lenart
2001-01-31 20:46     ` Rik van Riel
2001-01-31 20:58       ` Mark Hahn
2001-02-03 19:41     ` Paul Gortmaker
     [not found] <cs.lists.linux-kernel/3A72804A.E6052E1B@linux.com>
2001-01-27 10:14 ` Ion Badulescu
2001-01-27 11:45   ` David Ford
2001-02-01  1:26 Chris Adams

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=3A72804A.E6052E1B@linux.com \
    --to=david@linux.com \
    --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;
as well as URLs for NNTP newsgroup(s).