mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: "Isaac J. Manjarres" <isaacmanjarres@google.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	John Ogness <john.ogness@linutronix.de>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	surenb@google.com, kernel-team@android.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] printk: Improve memory usage logging during boot
Date: Tue, 1 Oct 2024 17:46:31 +0200	[thread overview]
Message-ID: <ZvwZV5MDlQYGJv9N@pathway.suse.cz> (raw)
In-Reply-To: <20240930184826.3595221-1-isaacmanjarres@google.com>

On Mon 2024-09-30 11:48:24, Isaac J. Manjarres wrote:
> When the initial printk ring buffer size is updated, setup_log_buf()
> allocates a new ring buffer, as well as a set of meta-data structures
> for the new ring buffer. The function also emits the new size of the
> ring buffer, but not the size of the meta-data structures.
> 
> This makes it difficult to assess how changing the log buffer size
> impacts memory usage during boot.
> 
> For instance, increasing the ring buffer size from 512 KB to 1 MB
> through the command line yields an increase of 2304 KB in reserved
> memory at boot, while the only obvious change is the 512 KB
> difference in the ring buffer sizes:
> 
> log_buf_len=512K:
> 
> printk: log_buf_len: 524288 bytes
> Memory: ... (... 733252K reserved ...)
> 
> log_buf_len=1M:
> 
> printk: log_buf_len: 1048576 bytes
> Memory: ... (... 735556K reserved ...)
> 
> This is because of how the size of the meta-data structures scale with
> the size of the ring buffer.
> 
> Even when there aren't changes to the printk ring buffer size (i.e. the
> initial size ==  1 << CONFIG_LOG_BUF_SHIFT), it is impossible to tell
> how much memory is consumed by the printk ring buffer during boot.
> 
> Therefore, unconditionally log the sizes of the printk ring buffer
> and its meta-data structures, so that it's easier to understand
> how changing the log buffer size (either through the command line or
> by changing CONFIG_LOG_BUF_SHIFT) affects boot time memory usage.
> 
> With the new logs, it is much easier to see exactly why the memory
> increased by 2304 KB:
> 
> log_buf_len=512K:
> 
> printk: log_buf_len: 524288 bytes
> printk: prb_descs size: 393216 bytes
> printk: printk_infos size: 1441792 bytes

This should get updated to the new format.
If I count correctly then it should be:

printk: log buffer data + meta data: 524288 + 1835008 = 2359296 bytes

> Memory: ... (... 733252K reserved ...)
> 
> log_buf_len=1M:
> 
> printk: log_buf_len: 1048576 bytes
> printk: prb_descs size: 786432 bytes
> printk: printk_infos size: 2883584 bytes

and here:

printk: log buffer data + meta data: 1048576 + 3670016 = 4718592 bytes

> Memory: ... (... 735556K reserved ...)
>
> Signed-off-by: Isaac J. Manjarres <isaacmanjarres@google.com>

Otherwise, it looks good. With the updated commit message:

Reviewed-by: Petr Mladek <pmladek@suse.com>
Tested-by: Petr Mladek <pmladek@suse.com>


Note need to send v3. I could update the commit message when committing
the patch.

I am going to wait few days for a potential another review
before pushing.

Best Regards,
Petr

  reply	other threads:[~2024-10-01 15:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-30 18:48 Isaac J. Manjarres
2024-10-01 15:46 ` Petr Mladek [this message]
2024-10-02 18:04   ` Isaac Manjarres
2024-10-15 12:47     ` Isaac Manjarres
2024-10-16 10:24       ` Petr Mladek
2024-10-16 16:38         ` Isaac Manjarres
2024-12-01 11:40   ` Geert Uytterhoeven
2024-12-03  9:42     ` Petr Mladek
2024-12-04 17:17       ` John Ogness

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=ZvwZV5MDlQYGJv9N@pathway.suse.cz \
    --to=pmladek@suse.com \
    --cc=isaacmanjarres@google.com \
    --cc=john.ogness@linutronix.de \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.org \
    --cc=surenb@google.com \
    /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®