From: Rong Chen <rong.a.chen@intel.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: Jia-Ju Bai <baijiaju1990@gmail.com>,
shaggy@kernel.org, jfs-discussion@lists.sourceforge.net,
linux-kernel@vger.kernel.org, lkp@lists.01.org,
Markus.Elfring@web.de
Subject: Re: [Jfs-discussion] [fs] 05c5a0273b: netperf.Throughput_total_tps -71.8% regression
Date: Thu, 14 May 2020 13:12:18 +0800 [thread overview]
Message-ID: <5d4fbe21-7959-d53f-76c5-ed0299d8db23@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.22.395.2005132123020.14542@trent.utfs.org>
On 5/14/20 12:27 PM, Christian Kujau wrote:
> On Tue, 12 May 2020, kernel test robot wrote:
>> FYI, we noticed a -71.8% regression of netperf.Throughput_total_tps due to commit:
> As noted in this report, netperf is used to "measure various aspect of
> networking performance". Are we sure the bisect is correct? JFS is a
> filesystem and is not touching net/ in any way. So, having not attempted
> to reproduce this, maybe the JFS commit is a red herring?
>
> C.
Hi,
The commit also causes -74.6% regression of will-it-scale.per_thread_ops:
in testcase: will-it-scale
on test machine: 8 threads Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz with 16G memory
with following parameters:
nr_task: 100%
mode: thread
test: unlink2
cpufreq_governor: performance
ucode: 0x21
I'll send another report for this regression.
Best Regards,
Rong Chen
next prev parent reply other threads:[~2020-05-14 5:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 14:50 [PATCH v2] fs: jfs: fix a possible data race in txBegin() Jia-Ju Bai
2020-05-12 3:09 ` [fs] 05c5a0273b: netperf.Throughput_total_tps -71.8% regression kernel test robot
2020-05-14 4:27 ` [Jfs-discussion] " Christian Kujau
2020-05-14 5:12 ` Rong Chen [this message]
[not found] ` <20200514154251.18184-1-hdanton@sina.com>
2020-05-15 7:34 ` Jia-Ju Bai
2020-05-14 5:13 ` [fs] 05c5a0273b: will-it-scale.per_thread_ops -74.6% regression kernel test robot
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=5d4fbe21-7959-d53f-76c5-ed0299d8db23@intel.com \
--to=rong.a.chen@intel.com \
--cc=Markus.Elfring@web.de \
--cc=baijiaju1990@gmail.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
--cc=lkp@lists.01.org \
--cc=shaggy@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox