From: Gabor Lenart <lgb@lgb.hu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH/REQ] Increase kmsg buffer from 16K to 32K, kernel/printk.c
Date: Wed, 31 Jan 2001 18:21:24 +0100 [thread overview]
Message-ID: <20010131182124.A1890@supervisor.hu> (raw)
In-Reply-To: <3A72804A.E6052E1B@linux.com> <E14O0hv-0002hY-00@the-village.bc.nu>
In-Reply-To: <E14O0hv-0002hY-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Wed, Jan 31, 2001 at 05:06:07PM +0000
On Wed, Jan 31, 2001 at 05:06:07PM +0000, Alan Cox wrote:
> > 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.
>
> Thats just an indication that 2.4.x is currently printking too much crap on
> boot
Would it be possible to grow and shring that buffer on demand? Let's say
we have a default size and let it grow to a maximum value. After some
timeout, buffer size can be shrinked to default value if it's enough at
that moment. Or something similar.
--
--[ Gábor Lénárt ]---[ Vivendi Telecom Hungary ]--[ lgb@supervisor.hu ]--
U have 8 bit comp or chip of them and it's unused or to be sold? Call me!
-------[ +36 30 2270823 ]------> LGB <-----[ Linux/UNIX/8bit 4ever ]-----
-
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/
next prev parent reply other threads:[~2001-01-31 17:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-27 8:01 [PATCH/REQ] Increase kmsg buffer from 16K to 32K, kernel/printk.c David Ford
2001-01-31 17:06 ` Alan Cox
2001-01-31 17:19 ` Maciej W. Rozycki
2001-01-31 23:12 ` David Ford
2001-01-31 17:21 ` Gabor Lenart [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=20010131182124.A1890@supervisor.hu \
--to=lgb@lgb.hu \
--cc=alan@lxorguk.ukuu.org.uk \
--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