mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Edward Kuns <ekuns@kilroy.chi.il.us>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Edward Kuns <ekuns@kilroy.chi.il.us>
Subject: Larger circular printk log message buffer for kernel?
Date: 09 Feb 2003 22:20:03 -0600	[thread overview]
Message-ID: <1044850803.14790.18.camel@kilroy.chi.il.us> (raw)

Please CC me for responses.

I'm willing to make a patch if it is likely to be accepted into the
kernel.  Since we have so many subsystems that spit out kilobytes of
messages, by the time my system has booted up I have already lost some
of the most important boot messages!  (APIC, for example)

I found the important part located in kernel/printk.c as follows in
2.4.21-pre3-ac2:

#if defined(CONFIG_MULTIQUAD) || defined(CONFIG_IA64)
#define LOG_BUF_LEN	(65536)
#elif defined(CONFIG_ARCH_S390)
#define LOG_BUF_LEN	(131072)
#elif defined(CONFIG_SMP)
#define LOG_BUF_LEN	(32768)
#else	
#define LOG_BUF_LEN	(16384)			/* This must be a power of two */
#endif

I changed the last one to 32768 and now I see all my boot messages.  I
imagine that people would be against doubling the last two buffers (that
is, SMP = 64k, else = 32k) on all systems.  But 16k is simply too small
for anyone using RAID or USB or APIC or other "noisy" subsystems.
RAID/md is by far the noisiest boot-time subsystem I have configured.

Ideas?  Perhaps a kernel config multiplier defaulting to "1" that can be
changed in "make config" to 2, 4, 8, ...?  I'm willing to do the work
for this, but only if it seems likely to be accepted.  Are there other,
better options?

On systems with large amounts of memory, surely we can afford to give
more of it to the kernel's log message buffer!


	Eddie

-- 
  Eddie Kuns  |  Home: ekuns@kilroy.chi.il.us
--------------/  URL:  (none at the moment)
  "Ah, savory cheese puffs, made inedible by time and fate."  -- The Tick

             reply	other threads:[~2003-02-10  4:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-10  4:20 Edward Kuns [this message]
2003-02-10  4:26 ` Valdis.Kletnieks

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=1044850803.14790.18.camel@kilroy.chi.il.us \
    --to=ekuns@kilroy.chi.il.us \
    --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

all inboxes | Powered by JetHome®