All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Feng Tang <feng.tang@intel.com>,
	kernel test robot <oliver.sang@intel.com>,
	Jonathan Lemon <bsd@fb.com>, Tony Luck <tony.luck@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	x86@kernel.org, lkp@lists.01.org, lkp@intel.com,
	ying.huang@intel.com, zhengjun.xing@intel.com
Subject: Re: [x86/mce]  7bb39313cd:  netperf.Throughput_tps -4.5% regression
Date: Tue, 19 Jan 2021 11:02:55 +0100	[thread overview]
Message-ID: <20210119100255.GC27433@zn.tnic> (raw)
In-Reply-To: <20210119042721.GA12664@paulmck-ThinkPad-P72>

On Mon, Jan 18, 2021 at 08:27:21PM -0800, Paul E. McKenney wrote:
> I bet that the results vary depending on the type of CPU, and also on
> the kernel address-space layout, which of course also varies based on
> the Kconfig options.  Let's see how the maintainers would like to proceed.

So I ran the "reproduce" script in the original mail on a KBL box here
with the .config tailored for it:

cpu family      : 6
model           : 158
model name      : Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz
stepping        : 12
microcode       : 0xd6

and I get mixed results. But I'd need to know how exactly they generate
the metrics "netperf.Throughput_total_tps" and "netperf.Throughput_tps"

Feng?

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: lkp@lists.01.org
Subject: Re: [x86/mce] 7bb39313cd: netperf.Throughput_tps -4.5% regression
Date: Tue, 19 Jan 2021 11:02:55 +0100	[thread overview]
Message-ID: <20210119100255.GC27433@zn.tnic> (raw)
In-Reply-To: <20210119042721.GA12664@paulmck-ThinkPad-P72>

[-- Attachment #1: Type: text/plain, Size: 799 bytes --]

On Mon, Jan 18, 2021 at 08:27:21PM -0800, Paul E. McKenney wrote:
> I bet that the results vary depending on the type of CPU, and also on
> the kernel address-space layout, which of course also varies based on
> the Kconfig options.  Let's see how the maintainers would like to proceed.

So I ran the "reproduce" script in the original mail on a KBL box here
with the .config tailored for it:

cpu family      : 6
model           : 158
model name      : Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz
stepping        : 12
microcode       : 0xd6

and I get mixed results. But I'd need to know how exactly they generate
the metrics "netperf.Throughput_total_tps" and "netperf.Throughput_tps"

Feng?

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2021-01-19 10:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12 14:21 [x86/mce] 7bb39313cd: netperf.Throughput_tps -4.5% regression kernel test robot
2021-01-12 14:21 ` kernel test robot
2021-01-12 14:14 ` Borislav Petkov
2021-01-12 14:14   ` Borislav Petkov
     [not found]   ` <20210116035251.GB29609@shbuild999.sh.intel.com>
2021-01-16 15:34     ` Paul E. McKenney
2021-01-16 15:34       ` Paul E. McKenney
2021-01-16 16:09       ` Feng Tang
2021-01-16 16:09         ` Feng Tang
2021-01-19  4:27         ` Paul E. McKenney
2021-01-19  4:27           ` Paul E. McKenney
2021-01-19 10:02           ` Borislav Petkov [this message]
2021-01-19 10:02             ` Borislav Petkov
2021-01-19 12:15             ` Feng Tang
2021-01-19 12:15               ` Feng Tang
2021-01-19 13:17               ` Borislav Petkov
2021-01-19 13:17                 ` Borislav Petkov
2021-01-19 15:09                 ` Feng Tang
2021-01-19 15:09                   ` Feng Tang
2021-01-19 15:33                   ` Borislav Petkov
2021-01-19 15:33                     ` Borislav Petkov
2021-01-20  5:48                     ` Feng Tang
2021-01-20  5:48                       ` Feng Tang

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=20210119100255.GC27433@zn.tnic \
    --to=bp@alien8.de \
    --cc=bsd@fb.com \
    --cc=feng.tang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lkp@lists.01.org \
    --cc=oliver.sang@intel.com \
    --cc=paulmck@kernel.org \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    --cc=ying.huang@intel.com \
    --cc=zhengjun.xing@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 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.