From: Kees Cook <keescook@chromium.org>
To: kernel test robot <xiaolong.ye@intel.com>
Cc: Guillaume Knispel <guillaume.knispel@supersonicimagine.com>,
Andrew Morton <akpm@linux-foundation.org>,
Manfred Spraul <manfred@colorfullife.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Alexey Dobriyan <adobriyan@gmail.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Serge Hallyn <serge@hallyn.com>, Andrey Vagin <avagin@openvz.org>,
Marc Pardo <marc.pardo@supersonicimagine.com>,
LKML <linux-kernel@vger.kernel.org>, LKP <lkp@01.org>
Subject: Re: [lkp-robot] [ipc] cb6268f05d: reaim.jobs_per_min 865% improvement
Date: Mon, 14 Aug 2017 10:59:02 -0700 [thread overview]
Message-ID: <CAGXu5jKpW7asmWOtQdnrGAdYjgw1gS+VmCC315Yt15b+s+CdOQ@mail.gmail.com> (raw)
In-Reply-To: <20170814060507.GE23258@yexl-desktop>
On Sun, Aug 13, 2017 at 11:05 PM, kernel test robot
<xiaolong.ye@intel.com> wrote:
>
> Greeting,
>
> FYI, we noticed a 865% improvement of reaim.jobs_per_min due to commit:
>
>
> commit: cb6268f05df684e00607762fd8ad95d515e2407f ("ipc: optimize semget/shmget/msgget for lots of keys")
> url: https://github.com/0day-ci/linux/commits/Guillaume-Knispel/ipc-optimize-semget-shmget-msgget-for-lots-of-keys/20170731-170031
Impressive!
-Kees
--
Kees Cook
Pixel Security
prev parent reply other threads:[~2017-08-14 17:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 8:42 [PATCH] ipc: optimize semget/shmget/msgget for lots of keys Guillaume Knispel
2017-07-31 15:45 ` Davidlohr Bueso
2017-08-01 1:17 ` Guillaume Knispel
2017-08-01 15:51 ` Davidlohr Bueso
2017-08-02 20:06 ` Davidlohr Bueso
2017-08-03 17:14 ` Guillaume Knispel
2017-08-07 17:33 ` Davidlohr Bueso
2017-08-07 18:21 ` Davidlohr Bueso
2017-08-09 16:15 ` Guillaume Knispel
2017-08-14 6:05 ` [lkp-robot] [ipc] cb6268f05d: reaim.jobs_per_min 865% improvement kernel test robot
2017-08-14 17:59 ` Kees Cook [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=CAGXu5jKpW7asmWOtQdnrGAdYjgw1gS+VmCC315Yt15b+s+CdOQ@mail.gmail.com \
--to=keescook@chromium.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=avagin@openvz.org \
--cc=bigeasy@linutronix.de \
--cc=dave@stgolabs.net \
--cc=ebiederm@xmission.com \
--cc=guillaume.knispel@supersonicimagine.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=manfred@colorfullife.com \
--cc=marc.pardo@supersonicimagine.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=serge@hallyn.com \
--cc=xiaolong.ye@intel.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).