From: Catalin Marinas <catalin.marinas@arm.com>
To: Nicolas Boichat <drinkcat@chromium.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Kees Cook <keescook@chromium.org>, Petr Mladek <pmladek@suse.com>,
Thomas Gleixner <tglx@linutronix.de>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
Joe Lawrence <joe.lawrence@redhat.com>,
Uladzislau Rezki <urezki@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Dmitry Vyukov <dvyukov@google.com>,
Andrey Ryabinin <aryabinin@virtuozzo.com>
Subject: Re: [PATCH] kmemleak: Increase DEBUG_KMEMLEAK_EARLY_LOG_SIZE default to 16K
Date: Tue, 30 Jul 2019 16:42:05 +0100 [thread overview]
Message-ID: <20190730154204.GC15386@arrakis.emea.arm.com> (raw)
In-Reply-To: <20190730154027.101525-1-drinkcat@chromium.org>
On Tue, Jul 30, 2019 at 11:40:27PM +0800, Nicolas Boichat wrote:
> The current default value (400) is too low on many systems (e.g.
> some ARM64 platform takes up 1000+ entries).
>
> syzbot uses 16000 as default value, and has proved to be enough
> on beefy configurations, so let's pick that value.
>
> This consumes more RAM on boot (each entry is 160 bytes, so
> in total ~2.5MB of RAM), but the memory would later be freed
> (early_log is __initdata).
>
> Suggested-by: Dmitry Vyukov <dvyukov@google.com>
> Signed-off-by: Nicolas Boichat <drinkcat@chromium.org>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
next prev parent reply other threads:[~2019-07-30 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 15:40 [PATCH] kmemleak: Increase DEBUG_KMEMLEAK_EARLY_LOG_SIZE default to 16K Nicolas Boichat
2019-07-30 15:42 ` Catalin Marinas [this message]
2019-07-30 16:23 ` Dmitry Vyukov
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=20190730154204.GC15386@arrakis.emea.arm.com \
--to=catalin.marinas@arm.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=aryabinin@virtuozzo.com \
--cc=drinkcat@chromium.org \
--cc=dvyukov@google.com \
--cc=joe.lawrence@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=pmladek@suse.com \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=urezki@gmail.com \
--cc=yamada.masahiro@socionext.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;
as well as URLs for NNTP newsgroup(s).