From: Isaac Manjarres <isaacmanjarres@google.com>
To: Petr Mladek <pmladek@suse.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: Wed, 2 Oct 2024 11:04:48 -0700 [thread overview]
Message-ID: <Zv2LQLsIC1y0bCDL@google.com> (raw)
In-Reply-To: <ZvwZV5MDlQYGJv9N@pathway.suse.cz>
On Tue, Oct 01, 2024 at 05:46:31PM +0200, Petr Mladek wrote:
> On Mon 2024-09-30 11:48:24, Isaac J. Manjarres wrote:
> > 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
Sorry, I forgot to do that; thanks for catching it. Yes, the
calculation is correct.
> > 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
This is also correct.
> > 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.
Thank you Petr for your review and for picking this up! I really
appreciate it.
Thanks,
Isaac
next prev parent reply other threads:[~2024-10-02 18:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 18:48 [PATCH v2] printk: Improve memory usage logging during boot Isaac J. Manjarres
2024-10-01 15:46 ` Petr Mladek
2024-10-02 18:04 ` Isaac Manjarres [this message]
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=Zv2LQLsIC1y0bCDL@google.com \
--to=isaacmanjarres@google.com \
--cc=john.ogness@linutronix.de \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--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