linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Kujau <lists@nerdbynature.de>
To: kernel test robot <rong.a.chen@intel.com>
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: Wed, 13 May 2020 21:27:26 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.22.395.2005132123020.14542@trent.utfs.org> (raw)
In-Reply-To: <20200512030929.GA5770@shao2-debian>

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.
-- 
BOFH excuse #50:

Change in Earth's rotational speed

  reply	other threads:[~2020-05-14  4:35 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   ` Christian Kujau [this message]
2020-05-14  5:12     ` [Jfs-discussion] " Rong Chen
     [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=alpine.DEB.2.22.395.2005132123020.14542@trent.utfs.org \
    --to=lists@nerdbynature.de \
    --cc=Markus.Elfring@web.de \
    --cc=baijiaju1990@gmail.com \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@lists.01.org \
    --cc=rong.a.chen@intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).