From: Eric Biggers <ebiggers@kernel.org>
To: kernel test robot <rong.a.chen@intel.com>
Cc: Theodore Ts'o <tytso@mit.edu>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
lkp@lists.01.org
Subject: Re: [fscrypt] 22d94f493b: will-it-scale.per_thread_ops 1.7% improvement
Date: Mon, 9 Mar 2020 12:09:39 -0700 [thread overview]
Message-ID: <20200309190939.GD1073@sol.localdomain> (raw)
In-Reply-To: <20200308140241.GP5972@shao2-debian>
On Sun, Mar 08, 2020 at 10:02:41PM +0800, kernel test robot wrote:
> Greeting,
>
> FYI, we noticed a 1.7% improvement of will-it-scale.per_thread_ops due to commit:
>
>
> commit: 22d94f493bfb408fdd764f7b1d0363af2122fba5 ("fscrypt: add FS_IOC_ADD_ENCRYPTION_KEY ioctl")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>
> in testcase: will-it-scale
> on test machine: 192 threads Intel(R) Xeon(R) Platinum 9242 CPU @ 2.30GHz with 192G memory
> with following parameters:
>
> nr_task: 50%
> mode: thread
> test: poll2
> cpufreq_governor: performance
> ucode: 0x500002c
>
> 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
This looks like a flaky test. That commit shouldn't have had any effect on this
performance test, either positive or negative.
- Eric
prev parent reply other threads:[~2020-03-09 19:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-08 14:02 [fscrypt] 22d94f493b: will-it-scale.per_thread_ops 1.7% improvement kernel test robot
2020-03-09 19:09 ` Eric Biggers [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=20200309190939.GD1073@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@lists.01.org \
--cc=rong.a.chen@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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