From: Oliver Sang <oliver.sang@intel.com>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: Anna-Maria Behnsen <anna-maria@linutronix.de>,
<oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, <x86@kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>, <ying.huang@intel.com>,
<feng.tang@intel.com>, <fengwei.yin@intel.com>,
<oliver.sang@intel.com>
Subject: Re: [tip:timers/core] [timers] 7ee9887703: netperf.Throughput_Mbps -1.2% regression
Date: Mon, 4 Mar 2024 10:13:00 +0800 [thread overview]
Message-ID: <ZeUuLPXfLCmB39qq@xsang-OptiPlex-9020> (raw)
In-Reply-To: <ZeUWreWcp4UWQ081@pavilion.home>
hi, Frederic Weisbecker,
On Mon, Mar 04, 2024 at 01:32:45AM +0100, Frederic Weisbecker wrote:
> Le Fri, Mar 01, 2024 at 04:09:24PM +0800, kernel test robot a écrit :
> >
> >
> > Hello,
> >
> > kernel test robot noticed a -1.2% regression of netperf.Throughput_Mbps on:
> >
> >
> > commit: 7ee988770326fca440472200c3eb58935fe712f6 ("timers: Implement the hierarchical pull model")
> > https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git timers/core
> >
> > testcase: netperf
> > test machine: 128 threads 2 sockets Intel(R) Xeon(R) Gold 6338 CPU @ 2.00GHz (Ice Lake) with 256G memory
> > parameters:
> >
> > ip: ipv4
> > runtime: 300s
> > nr_threads: 200%
> > cluster: cs-localhost
> > test: SCTP_STREAM
> > cpufreq_governor: performance
> >
> >
> >
> >
> > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > the same patch/commit), kindly add following tags
> > | Reported-by: kernel test robot <oliver.sang@intel.com>
> > | Closes: https://lore.kernel.org/oe-lkp/202403011511.24defbbd-oliver.sang@intel.com
> >
> >
> > Details are as below:
> > -------------------------------------------------------------------------------------------------->
> >
> >
> > The kernel config and materials to reproduce are available at:
> > https://download.01.org/0day-ci/archive/20240301/202403011511.24defbbd-oliver.sang@intel.com
> >
> > =========================================================================================
> > cluster/compiler/cpufreq_governor/ip/kconfig/nr_threads/rootfs/runtime/tbox_group/test/testcase:
> > cs-localhost/gcc-12/performance/ipv4/x86_64-rhel-8.3/200%/debian-12-x86_64-20240206.cgz/300s/lkp-icl-2sp2/SCTP_STREAM/netperf
> >
> > commit:
> > 57e95a5c41 ("timers: Introduce function to check timer base is_idle flag")
> > 7ee9887703 ("timers: Implement the hierarchical pull model")
>
> Is this something that is observed also with the commits that follow in this
> branch?
when this bisect done, we also tested the tip of timers/core branch at that time
8b3843ae3634b vdso/datapage: Quick fix - use asm/page-def.h for ARM64
the regression still exists on it:
57e95a5c4117dc6a 7ee988770326fca440472200c3e 8b3843ae3634b472530fb69c386
---------------- --------------------------- ---------------------------
%stddev %change %stddev %change %stddev
\ | \ | \
4.10 -1.2% 4.05 -1.2% 4.05 netperf.ThroughputBoth_Mbps
1049 -1.2% 1037 -1.2% 1036 netperf.ThroughputBoth_total_Mbps
4.10 -1.2% 4.05 -1.2% 4.05 netperf.Throughput_Mbps
1049 -1.2% 1037 -1.2% 1036 netperf.Throughput_total_Mbps
>
> Ie: would it be possible to compare instead:
>
> 57e95a5c4117 (timers: Introduce function to check timer base is_idle flag)
> VS
> b2cf7507e186 (timers: Always queue timers on the local CPU)
>
> Because the improvements introduced by 7ee9887703 are mostly relevant after
> b2cf7507e186.
got it. will test.
at the same time, we noticed current tip of timers/core is
a184d9835a0a6 (tip/timers/core) tick/sched: Fix build failure for CONFIG_NO_HZ_COMMON=n
though it seems irelevant, we will still get data for it.
>
> Thanks.
next prev parent reply other threads:[~2024-03-04 2:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 8:09 kernel test robot
2024-03-04 0:32 ` Frederic Weisbecker
2024-03-04 2:13 ` Oliver Sang [this message]
2024-03-04 11:28 ` Frederic Weisbecker
2024-03-05 2:17 ` Oliver Sang
2024-03-05 10:46 ` Frederic Weisbecker
2024-03-05 11:21 ` Frederic Weisbecker
2024-03-05 11:35 ` Frederic Weisbecker
2024-03-12 23:57 ` Frederic Weisbecker
2024-03-13 8:25 ` Thomas Gleixner
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=ZeUuLPXfLCmB39qq@xsang-OptiPlex-9020 \
--to=oliver.sang@intel.com \
--cc=anna-maria@linutronix.de \
--cc=feng.tang@intel.com \
--cc=fengwei.yin@intel.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=ying.huang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®