All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: kbuild-all@lists.01.org
Subject: Re: [linux-next:master 6188/10009] h8300-linux-ld: section .softirqentry.text VMA overlaps section .bss VMA
Date: Thu, 13 Aug 2020 10:49:15 +0900	[thread overview]
Message-ID: <20200813014915.GB2020879@jagdpanzerIV.localdomain> (raw)
In-Reply-To: <87364uchoz.fsf@jogness.linutronix.de>

[-- Attachment #1: Type: text/plain, Size: 670 bytes --]

On (20/08/10 23:36), John Ogness wrote:
> > Let's look at my test system using the original log buffer[*]:
> >
> > text: 30 kB
> > metadata: 14 kB
> > dict: 9 kB
> >
> > The text takes more than half of the space. But the difference is not
> > too huge. So decreasing CONFIG_LOG_BUF_SHIFT by one might be
> > acceptable.
> >
> > Also it might make sense to decrease the size of the dict ring by
> > two. I mean to have size of text:dict rings as 2:1.
> 
> Yes, I thought about that as well. Although it would be hard to justify
> any particular ratio since it depends on the system.

I think there will be some users of CONFIG_PRINTK_DICT_SIZE=0

	-ss

  parent reply	other threads:[~2020-08-13  1:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-22 15:07 [linux-next:master 6188/10009] h8300-linux-ld: section .softirqentry.text VMA overlaps section .bss VMA kernel test robot
2020-07-27 11:54 ` John Ogness
2020-08-05 15:35   ` Petr Mladek
2020-08-10 21:30     ` John Ogness
2020-08-11 10:32       ` Petr Mladek
2020-08-11 13:17         ` Steven Rostedt
2020-08-13  1:49       ` Sergey Senozhatsky [this message]
2020-08-11  8:24     ` Petr Mladek

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=20200813014915.GB2020879@jagdpanzerIV.localdomain \
    --to=sergey.senozhatsky@gmail.com \
    --cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.