From: kernel test robot <yi1.lai@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org, x86@kernel.org,
Ingo Molnar <mingo@kernel.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
aubrey.li@linux.intel.com, yu.c.chen@intel.com,
yi1.lai@intel.com
Subject: [tip:sched/core] [sched/fair] 9e3fa63360: stress-ng.spawn.ops_per_sec 12.8% regression
Date: Thu, 19 Nov 2026 15:17:06 +0800 [thread overview]
Message-ID: <202611191526.fc8f4ad6-lkp@intel.com> (raw)
Hello,
kernel test robot noticed a 12.8% regression of stress-ng.spawn.ops_per_sec on:
commit: 9e3fa63360bc9ac17619ff076d38d29f57edeb0e ("sched/fair: Rework/fix task_h_load()") https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git sched/core
testcase: stress-ng
config: x86_64-rhel-9.4
compiler: gcc-14
test machine: 224 threads 2 sockets Intel(R) Xeon(R) Platinum 8480CTDX (Sapphire Rapids) with 256G memory
parameters:
nr_threads: 100%
testtime: 60s
test: spawn
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 <yi1.lai@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202611191526.fc8f4ad6-lkp@intel.com
Details are as below:
-------------------------------------------------------------------------------------------------->
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20261119/202611191526.fc8f4ad6-lkp@intel.com
=========================================================================================
compiler/cpufreq_governor/kconfig/nr_threads/rootfs/tbox_group/test/testcase/testtime:
gcc-14/performance/x86_64-rhel-9.4/100%/debian-13-x86_64-20250902.cgz/lkp-spr-r02/spawn/stress-ng/60s
commit:
e0aeaebb8a ("sched/fair: Extend for_each_sched_entity() with a back-link")
9e3fa63360 ("sched/fair: Rework/fix task_h_load()")
e0aeaebb8a46c276 9e3fa63360bc9ac17619ff076d3
---------------- ---------------------------
%stddev %change %stddev
\ | \
1067726 -12.8% 930818 stress-ng.spawn.ops
17811 -12.8% 15528 stress-ng.spawn.ops_per_sec
1053999 ± 2% -11.6% 931631 stress-ng.time.involuntary_context_switches
885751 ± 9% +109.9% 1859162 ± 2% stress-ng.time.major_page_faults
5.971e+08 -12.9% 5.201e+08 stress-ng.time.minor_page_faults
19469 -1.4% 19196 stress-ng.time.percent_of_cpu_this_job_got
9503 +1.6% 9652 stress-ng.time.system_time
2196 -14.2% 1884 stress-ng.time.user_time
16430012 ± 4% +24.0% 20370954 stress-ng.time.voluntary_context_switches
Disclaimer:
Results have been estimated based on internal Intel analysis and are provided
for informational purposes only. Any difference in system hardware or software
design or configuration may affect actual performance.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-11-19 7:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202611191526.fc8f4ad6-lkp@intel.com \
--to=yi1.lai@intel.com \
--cc=aubrey.li@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=vincent.guittot@linaro.org \
--cc=x86@kernel.org \
--cc=yu.c.chen@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®