[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACT4Y+ZRoSeBw=NUxvnLR+GAHweDgyV+3YkzeZiW3f85STqMpQ@mail.gmail.com>
Date: Tue, 30 Jul 2019 18:23:44 +0200
From: Dmitry Vyukov <dvyukov@...gle.com>
To: Catalin Marinas <catalin.marinas@....com>
Cc: Nicolas Boichat <drinkcat@...omium.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Kees Cook <keescook@...omium.org>,
Petr Mladek <pmladek@...e.com>,
Thomas Gleixner <tglx@...utronix.de>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
Joe Lawrence <joe.lawrence@...hat.com>,
Uladzislau Rezki <urezki@...il.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
LKML <linux-kernel@...r.kernel.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Andrey Ryabinin <aryabinin@...tuozzo.com>
Subject: Re: [PATCH] kmemleak: Increase DEBUG_KMEMLEAK_EARLY_LOG_SIZE default
to 16K
On Tue, Jul 30, 2019 at 5:42 PM Catalin Marinas <catalin.marinas@....com> wrote:
>
> 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@...gle.com>
> > Signed-off-by: Nicolas Boichat <drinkcat@...omium.org>
>
> Acked-by: Catalin Marinas <catalin.marinas@....com>
Acked-by: Dmitry Vyukov <dvyukov@...gle.com>
Powered by blists - more mailing lists