From: Petr Mladek <pmladek@suse.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
linux-kernel@vger.kernel.org,
John Ogness <john.ogness@linutronix.de>,
Linus Torvalds <torvalds@linuxfoundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-embedded@vger.kernel.org
Subject: Re: [PATCH v2 2/2] init/Kconfig: Increase default log buffer size from 128 KB to 512 KB
Date: Fri, 30 Oct 2020 16:28:10 +0100 [thread overview]
Message-ID: <20201030152810.GA20201@alley> (raw)
In-Reply-To: <92a13465-d133-0b39-f64b-7074dbbb3fcc@molgen.mpg.de>
On Thu 2020-10-29 23:16:01, Paul Menzel wrote:
> Dear Petr,
>
>
> Am 11.08.20 um 12:53 schrieb Petr Mladek:
> > On Tue 2020-08-11 11:29:24, Paul Menzel wrote:
> > > Commit f17a32e97e (let LOG_BUF_SHIFT default to 17) from 2008 was the
> > > last time, the the default log buffer size bump was increased.
> > >
> > > Machines have evolved, and on current hardware, enough memory is
> > > present, and some devices have over 200 PCI devices, like a two socket
> > > Skylake-E server, resulting a lot of lines.
> > >
> > > Therefore, increase the default from 128 KB to 512 KB. Anyone, with
> > > limited memory, can still lower it.
> > >
> > > --- a/init/Kconfig
> > > +++ b/init/Kconfig
> > > @@ -681,9 +681,9 @@ config IKHEADERS
> > > kheaders.ko is built which can be loaded on-demand to get access to headers.
> > > config LOG_BUF_SHIFT
> > > - int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
> > > + int "Kernel log buffer size (17 => 128KB, 19 => 512KB)"
> > > range 12 25
> > > - default 17
> > > + default 19
> > > depends on PRINTK
> > > help
> > > Select the minimal kernel log buffer size as a power of 2.
> >
> > Honestly, I do not have experience with changing the defaults. People
> > hacking small devices might complain. Well, this can be solved
> > by increasing the default only when BASE_FULL is set.
> >
> > I am personally fine with increasing the default when BASE_FULL
> > is set. The amount of messages is growing over time because of
> > increasing complexity of both the hardware and software.
> > Fortunately also the amount of available memory is growing.
> >
> > Well, this should get discussed in wider audience. Adding some
> > people into CC.
> >
> > JFYI, it started with report of lost messages, see
> > https://lore.kernel.org/lkml/264bfbae-122d-9c41-59ea-6413f91bd866@molgen.mpg.de/
>
> As there was no objection, is it possible to apply the two patches, and
> maybe even get them into Linux 5.10?
Thanks for reminding me. I am sorry but it is too late for
5.10. Such a change should be added during the merge window.
Well, the size of the ring buffer has effectively increased in 5.10.
The lockless implementation stores strings and metadata separately.
It basically doubled the memory needs and people around embedded
devices were not happy, see
https://lore.kernel.org/r/CAMuHMdXHFFUrjRMEHnXXU8QQkgD9x_S6R3N0Q7Q4H2RSfy2GGw@mail.gmail.com
Please update the patch so that the default stays the same for
BASE_SMALL. Please, add Rasmus Villemoes
<linux@rasmusvillemoes.dk> and Geert Uytterhoeven
<geert@linux-m68k.org> into CC when you send it.
Best Regards,
Petr
next prev parent reply other threads:[~2020-10-30 15:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200811092924.6256-1-pmenzel@molgen.mpg.de>
[not found] ` <20200811092924.6256-2-pmenzel@molgen.mpg.de>
2020-08-11 10:53 ` [PATCH v2 2/2] init/Kconfig: Increase default log buffer size from 128 KB to 512 KB Petr Mladek
2020-10-29 22:16 ` Paul Menzel
2020-10-30 15:28 ` Petr Mladek [this message]
2020-10-30 8:01 ` Geert Uytterhoeven
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=20201030152810.GA20201@alley \
--to=pmladek@suse.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=john.ogness@linutronix.de \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=torvalds@linuxfoundation.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 read-only IMAP folder(s) and NNTP newsgroup(s).