From: Michal Hocko <mhocko@kernel.org>
To: kernel test robot <oliver.sang@intel.com>
Cc: Alexander Potapenko <glider@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Kees Cook <keescook@chromium.org>,
Christoph Lameter <cl@linux.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Kostya Serebryany <kcc@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Sandeep Patil <sspatil@android.com>,
Laura Abbott <labbott@redhat.com>,
Randy Dunlap <rdunlap@infradead.org>,
Jann Horn <jannh@google.com>, Mark Rutland <mark.rutland@arm.com>,
Marco Elver <elver@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, OTC LSE PnP <otc.lse.pnp@intel.com>
Subject: Re: [mm] 6471384af2: phoronix-test-suite.darktable.Masskrug.CPU-only.seconds 10.2% regression
Date: Thu, 9 Apr 2020 16:03:31 +0200 [thread overview]
Message-ID: <20200409140331.GK18386@dhcp22.suse.cz> (raw)
In-Reply-To: <20200409135029.GA2072@xsang-OptiPlex-9020>
On Thu 09-04-20 21:50:29, kernel test robot wrote:
> Greeting,
>
> FYI, we noticed a 10.2% regression of phoronix-test-suite.darktable.Masskrug.CPU-only.seconds due to commit:
>
>
> commit: 6471384af2a6530696fc0203bafe4de41a23c9ef ("mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[...]
> CONFIG_INIT_ON_ALLOC_DEFAULT_ON=y
> CONFIG_INIT_ON_FREE_DEFAULT_ON=y
So the feature is enabled by default and therefore this is no
regression. The feature is expected to have an overhead. It is nice to
see that quantified. These numbers roughly match those presented when
the feature was enabled.
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2020-04-09 14:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 13:50 kernel test robot
2020-04-09 14:03 ` Michal Hocko [this message]
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=20200409140331.GK18386@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=jannh@google.com \
--cc=kcc@google.com \
--cc=keescook@chromium.org \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@lists.01.org \
--cc=mark.rutland@arm.com \
--cc=ndesaulniers@google.com \
--cc=oliver.sang@intel.com \
--cc=otc.lse.pnp@intel.com \
--cc=rdunlap@infradead.org \
--cc=serge@hallyn.com \
--cc=sspatil@android.com \
--cc=torvalds@linux-foundation.org \
--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
all inboxes | Powered by JetHome®