From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: gene.heskett@verizon.net
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: increased verbosity in dmesg
Date: Sat, 16 Aug 2003 17:45:08 +0200 [thread overview]
Message-ID: <1061048708.624.0.camel@teapot.felipe-alfaro.com> (raw)
In-Reply-To: <200308161136.01133.gene.heskett@verizon.net>
On Sat, 2003-08-16 at 17:36, Gene Heskett wrote:
> >In 2.6.0-test, the ring bugger size is configurable. Just look for
> >CONFIG_LOG_BUF_SHIFT. The kernel ring size will be
> >2^CONFIG_LOG_BUF_SHIFT bytes, so for a CONFIG_LOG_BUF_SHIFT of 14,
> >you'll 2^14 or 16 KBytes.
>
> Which says that a setting of 15 would get 32k then.
> I take it this (for an i386 system) is the correct file to edit?
Yes, a value of 15 means 32KB. However, I don't recommend you setting
this value too high.
> kernel/ikconfig.h:CONFIG_LOG_BUF_SHIFT=14 \n\
> Mmmm, that says do not edit, auto-generated, so how about this one?
>
> include/config/log/buf/shift.h
>
> which contains only that single line. Its now 15 & we'll see.
No, no, you'll need to edit the ".config" file to reflect the changes.
next prev parent reply other threads:[~2003-08-16 15:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-16 8:38 Gene Heskett
2003-08-16 10:48 ` Martin Schlemmer
2003-08-16 12:51 ` Arkadiusz Miskiewicz
2003-08-16 15:07 ` Gene Heskett
2003-08-26 0:17 ` parport_pc Oops with 2.6.0-test3 Christian Kujau
2003-08-26 8:38 ` Andrew Morton
2003-08-26 23:03 ` Christian
2003-08-28 2:41 ` Christian Kujau
2003-08-16 11:02 ` increased verbosity in dmesg Felipe Alfaro Solana
2003-08-16 15:36 ` Gene Heskett
2003-08-16 15:45 ` Felipe Alfaro Solana [this message]
2003-08-16 16:01 ` Gene Heskett
2003-08-16 16:24 ` Felipe Alfaro Solana
2003-08-16 17:41 ` Randy.Dunlap
2003-08-16 17:57 ` Gene Heskett
2003-08-16 17:18 ` Randy.Dunlap
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=1061048708.624.0.camel@teapot.felipe-alfaro.com \
--to=felipe_alfaro@linuxmail.org \
--cc=gene.heskett@verizon.net \
--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®