From: Lou Langholtz <ldl@aros.net>
To: "Diego Calleja García" <aradorlinux@yahoo.es>
Cc: jgarzik@pobox.com, willy@debian.org, torvalds@osdl.org,
linux-kernel@vger.kernel.org, axboe@suse.de
Subject: Re: [PATCH] bio.c: reduce verbosity at boot
Date: Thu, 21 Aug 2003 19:11:22 -0600 [thread overview]
Message-ID: <3F456DBA.5040202@aros.net> (raw)
In-Reply-To: <20030821223141.74ccb89e.aradorlinux@yahoo.es>
Diego Calleja García wrote:
>El Thu, 21 Aug 2003 10:51:27 -0600 Lou Langholtz <ldl@aros.net> escribió:
>
>
>>How about using KERN_DEBUG and augmenting the dmesg store so that the
>>level that is saved is configurable? Even compile time configurable
>>seems reasonable to start. But axeing out even the possibility of boot
>>time info seems bad to me.
>>
>>
>Like this?
>(14) Kernel log buffer size (16 => 64KB, 17 => 128KB)
>Available at least in 2.6.0-test3 under "General setup"
>
>
Yes, except I was thinking for loglevel rather than size. Is a loglevel
option - as in only save printk's above level X in dmesg - already
available? I've seen other emails fly by on the printk system before so
this could well already be available. I haven't checked but was assuming
from the emails I'd seen so far that this didn't exist and was merely
suggesting this thinking it'd be an easy addition to the dmesg store.
prev parent reply other threads:[~2003-08-22 1:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-21 15:02 [PATCH] bio.c: reduce verbosity at boot Matthew Wilcox
2003-08-21 15:19 ` Jeff Garzik
2003-08-21 16:51 ` Lou Langholtz
2003-08-21 19:37 ` Matthew Wilcox
2003-08-21 19:55 ` Linus Torvalds
2003-08-22 6:10 ` David Lang
2003-08-25 18:28 ` Jens Axboe
2003-08-21 20:31 ` Diego Calleja García
2003-08-22 1:11 ` Lou Langholtz [this message]
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=3F456DBA.5040202@aros.net \
--to=ldl@aros.net \
--cc=aradorlinux@yahoo.es \
--cc=axboe@suse.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=willy@debian.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