From: Kees Cook <keescook@chromium.org>
To: lkp@lists.01.org
Subject: Re: [x86/entry] 8c5045f89b: will-it-scale.per_process_ops -12.9% regression
Date: Sat, 28 Mar 2020 15:19:28 -0700 [thread overview]
Message-ID: <202003281505.0F481D3@keescook> (raw)
In-Reply-To: <20200327074002.GV11705@shao2-debian>
[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]
On Fri, Mar 27, 2020 at 03:40:02PM +0800, kernel test robot wrote:
> Greeting,
>
> FYI, we noticed a -12.9% regression of will-it-scale.per_process_ops due to commit:
>
>
> commit: 8c5045f89b181a4412b698cafc9dc257192a3a65 ("x86/entry: Enable random_kstack_offset support")
> https://git.kernel.org/cgit/linux/kernel/git/kees/linux.git kspp/stack/offset/agnostic/v1
>
> in testcase: will-it-scale
> on test machine: 288 threads Intel(R) Xeon Phi(TM) CPU 7295 @ 1.50GHz with 80G memory
> with following parameters:
>
> nr_task: 100%
> mode: process
> test: lseek1
> cpufreq_governor: performance
> ucode: 0x11
>
> test-description: Will It Scale takes a testcase and runs it from 1 through to n parallel copies to see if the testcase will scale. It builds both a process and threads based test in order to see any differences between the two.
> test-url: https://github.com/antonblanchard/will-it-scale
Whoa. I'll take a closer look. I fail to understand how this could be
happening. In this CONFIG the changes are a NOP. And that would be
true for both process and thread. O_o
--
Kees Cook
WARNING: multiple messages have this Message-ID (diff)
From: Kees Cook <keescook@chromium.org>
To: kernel test robot <rong.a.chen@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>, lkp@lists.01.org
Subject: Re: [x86/entry] 8c5045f89b: will-it-scale.per_process_ops -12.9% regression
Date: Sat, 28 Mar 2020 15:19:28 -0700 [thread overview]
Message-ID: <202003281505.0F481D3@keescook> (raw)
In-Reply-To: <20200327074002.GV11705@shao2-debian>
On Fri, Mar 27, 2020 at 03:40:02PM +0800, kernel test robot wrote:
> Greeting,
>
> FYI, we noticed a -12.9% regression of will-it-scale.per_process_ops due to commit:
>
>
> commit: 8c5045f89b181a4412b698cafc9dc257192a3a65 ("x86/entry: Enable random_kstack_offset support")
> https://git.kernel.org/cgit/linux/kernel/git/kees/linux.git kspp/stack/offset/agnostic/v1
>
> in testcase: will-it-scale
> on test machine: 288 threads Intel(R) Xeon Phi(TM) CPU 7295 @ 1.50GHz with 80G memory
> with following parameters:
>
> nr_task: 100%
> mode: process
> test: lseek1
> cpufreq_governor: performance
> ucode: 0x11
>
> test-description: Will It Scale takes a testcase and runs it from 1 through to n parallel copies to see if the testcase will scale. It builds both a process and threads based test in order to see any differences between the two.
> test-url: https://github.com/antonblanchard/will-it-scale
Whoa. I'll take a closer look. I fail to understand how this could be
happening. In this CONFIG the changes are a NOP. And that would be
true for both process and thread. O_o
--
Kees Cook
next prev parent reply other threads:[~2020-03-28 22:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 7:40 [x86/entry] 8c5045f89b: will-it-scale.per_process_ops -12.9% regression kernel test robot
2020-03-27 7:40 ` kernel test robot
2020-03-28 22:19 ` Kees Cook [this message]
2020-03-28 22:19 ` Kees Cook
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=202003281505.0F481D3@keescook \
--to=keescook@chromium.org \
--cc=lkp@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.