All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: K Prateek Nayak <kprateek.nayak@amd.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	<linux-kernel@vger.kernel.org>, <x86@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Andrea Righi <arighi@nvidia.com>, <aubrey.li@linux.intel.com>,
	<yu.c.chen@intel.com>, <oliver.sang@intel.com>
Subject: [tip:sched/core] [sched/topology]  9e005ed211: stress-ng.kill.ops_per_sec 4.6% regression
Date: Thu, 11 Jun 2026 10:19:20 +0800	[thread overview]
Message-ID: <202606111053.c484a580-lkp@intel.com> (raw)



Hello,

kernel test robot noticed a 4.6% regression of stress-ng.kill.ops_per_sec on:


commit: 9e005ed21152d4a4bb0ceea71045ff8a642a6feb ("sched/topology: Allow multiple domains to claim sched_domain_shared")
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: 256 threads 4 sockets INTEL(R) XEON(R) PLATINUM 8592+ (Emerald Rapids) with 256G memory
parameters:

	nr_threads: 100%
	testtime: 60s
	test: kill
	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/202606111053.c484a580-lkp@intel.com


Details are as below:
-------------------------------------------------------------------------------------------------->


The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260611/202606111053.c484a580-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-emr-2sp1/kill/stress-ng/60s

commit: 
  a26d9208c1 ("Merge branch 'sched/cache'")
  9e005ed211 ("sched/topology: Allow multiple domains to claim sched_domain_shared")

a26d9208c1376ac3 9e005ed21152d4a4bb0ceea7104 
---------------- --------------------------- 
         %stddev     %change         %stddev
             \          |                \  
     16542            -5.6%      15623        stress-ng.kill.kill_calls_per_sec
  66940342            -4.6%   63830711        stress-ng.kill.ops
   1116630            -4.6%    1064849        stress-ng.kill.ops_per_sec
     50279            +5.7%      53164        meminfo.KernelStack
     14019 ± 46%     -48.8%       7174 ± 70%  numa-vmstat.node2.nr_slab_reclaimable
     10643 ± 21%     +49.0%      15853 ± 19%  numa-vmstat.node3.nr_slab_reclaimable
     50278            +5.7%      53144        proc-vmstat.nr_kernel_stack
     74611            +1.0%      75344        proc-vmstat.nr_vmalloc
    613641            +5.5%     647439 ±  3%  proc-vmstat.pgfree
     56078 ± 46%     -48.8%      28697 ± 70%  numa-meminfo.node2.KReclaimable
     56078 ± 46%     -48.8%      28697 ± 70%  numa-meminfo.node2.SReclaimable
     42574 ± 21%     +49.1%      63467 ± 19%  numa-meminfo.node3.KReclaimable
     42574 ± 21%     +49.1%      63467 ± 19%  numa-meminfo.node3.SReclaimable
      0.03 ± 55%     -64.7%       0.01 ± 99%  sched_debug.cfs_rq:/.spread.avg
      0.26 ± 27%     -55.0%       0.12 ± 84%  sched_debug.cfs_rq:/.spread.stddev
      4715 ± 14%     -28.3%       3380 ± 44%  sched_debug.cpu.curr->pid.min
      0.32 ±  3%      -8.3%       0.30 ±  3%  sched_debug.cpu.nr_running.stddev
     22.17 ± 31%    +128.9%      50.75 ± 12%  sched_debug.cpu.nr_uninterruptible.max
      3.99 ± 14%     +55.6%       6.20 ±  4%  sched_debug.cpu.nr_uninterruptible.stddev




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-06-11  2:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-11  2:19 kernel test robot [this message]
2026-06-11  5:01 ` [tip:sched/core] [sched/topology] 9e005ed211: stress-ng.kill.ops_per_sec 4.6% regression Chen, Yu C

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=202606111053.c484a580-lkp@intel.com \
    --to=oliver.sang@intel.com \
    --cc=arighi@nvidia.com \
    --cc=aubrey.li@linux.intel.com \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=peterz@infradead.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 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.