On Tue, Jan 19, 2021 at 02:17:59PM +0100, Borislav Petkov wrote:
On Tue, Jan 19, 2021 at 08:15:05PM +0800, Feng Tang wrote:
> On Tue, Jan 19, 2021 at 11:02:55AM +0100, Borislav Petkov wrote:
> > 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
> > So I ran the "reproduce" script in the original mail on a KBL box
> > 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
> I will also try to find a similar KBL in 0day to run the job. This
> -4.5% comes from a CascadeLake AP which is 4 nodes, 96C/192T.
> > and I get mixed results. But I'd need to know how exactly they generate
> > the metrics "netperf.Throughput_total_tps" and
> > Feng?
> I have to admit I'm just a dumb user of 0day :) I'll leave this question
> to Philip/Oliver/Rong who are from 0day team.
> I assumed you've cloned the lkp-tests.git, and seems one Ruby file
is used to
> process the output of the netperf.
$ ../lkp-tests/stats/netperf < rc2.log
$ ../lkp-tests/stats/netperf < with-holdout.log
So this definitely depends on the .config because in my case, *with* the
holdout patch it is better vs plain 5.11-rc2.
Yes, that can happen. I started a 4 tasks netperf on a 4C/8T KBL desktop,
and also saw around 2% improvement. Both the kernel config and the
For the performance changes I have checked, sometimes the change can be
reproduced on platforms of different generations (the exact delta number
may differs), sometimes it can only be reproduced on one specific platform,
like some old generation, or special one like Xeon Phi.