From: Roman Zippel <zippel@linux-m68k.org>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: 76306.1226@compuserve.com, <linux-kernel@vger.kernel.org>
Subject: Re: Wanted: a limit on kernel log buffer size
Date: Mon, 7 Apr 2003 14:19:50 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.44.0304071416330.12110-100000@serv> (raw)
In-Reply-To: <33182.4.64.238.61.1049683748.squirrel@webmail.osdl.org>
Hi,
On Sun, 6 Apr 2003, Randy.Dunlap wrote:
> This is a multi-part answer. Say, 5 parts.
>
> a. If someone won't read the help text, how can we help them?
>
> b. If we make a 2 GB log buffer size a compile-time error, will
> they read that?
>
> c. If we make it a compile-time warning, will they read that?
>
> d. What limit(s) do you suggest? I can try to add some limits.
>
> e. This kind of config limiting should be done in the config system IMO.
> I've asked Roman for that capability....
While I don't mind adding limits, checking it at compile time certainly
won't hurt.
Even better would be a more dynamic solution, which can release unused
print buffer after booting.
bye, Roman
next prev parent reply other threads:[~2003-04-07 12:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-07 1:34 Wanted: a limit on kernel log buffer size Chuck Ebbert
2003-04-07 2:49 ` Randy.Dunlap
2003-04-07 3:35 ` Randy.Dunlap
2003-04-07 3:39 ` Robert Love
2003-04-07 4:32 ` Randy.Dunlap
2003-04-07 23:17 ` [PATCH] " Randy.Dunlap
2003-04-07 12:19 ` Roman Zippel [this message]
2003-04-07 8:55 Chuck Ebbert
2003-04-07 8:55 Chuck Ebbert
2003-04-07 16:24 ` Randy.Dunlap
2003-04-07 21:12 Chuck Ebbert
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=Pine.LNX.4.44.0304071416330.12110-100000@serv \
--to=zippel@linux-m68k.org \
--cc=76306.1226@compuserve.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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).