All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <yi1.lai@intel.com>
To: Tim Chen <tim.c.chen@linux.intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
	Hyunwoo Kim <imv4bel@gmail.com>,
	Zenghui Yu <zenghui.yu@linux.dev>, Chen Yu <yu.c.chen@intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-mm@kvack.org, aubrey.li@linux.intel.com, yi1.lai@intel.com
Subject: [linus:master] [sched/cache]  28f9c0e0a0: stress-ng.fd-race.ops_per_sec 5.2% improvement
Date: Fri, 9 Oct 2026 11:30:33 +0800	[thread overview]
Message-ID: <202610091149.c00cf9f2-lkp@intel.com> (raw)



Hello,

kernel test robot noticed a 5.2% improvement of stress-ng.fd-race.ops_per_sec on:

commit: 28f9c0e0a0b94c5d3e1b634db545f6e1f94858c5 ("sched/cache: Decouple sched_cache_group from mm to fix UAF") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master

testcase: stress-ng
config: x86_64-rhel-9.4
compiler: gcc-14
test machine: 256 threads 2 sockets GENUINE INTEL(R) XEON(R) (Sierra Forest) with 128G memory
parameters:

	nr_threads: 100%
	testtime: 60s
	test: fd-race
	cpufreq_governor: performance

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

The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20261009/202610091149.c00cf9f2-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-srf-2sp1/fd-race/stress-ng/60s

commit: 
  d6013e2465 ("sched/cache: Honor migrate_llc_task semantics in active load balance, to fix LLC mis-scheduling bug")
  28f9c0e0a0 ("sched/cache: Decouple sched_cache_group from mm to fix UAF")

d6013e2465d98d52 28f9c0e0a0b94c5d3e1b634db54
---------------- --------------------------- 
         %stddev     %change         %stddev
             \          |                \  
  28370042            +5.2%   29834431        stress-ng.fd-race.ops
    473267            +5.2%     497702        stress-ng.fd-race.ops_per_sec
    843367           +27.1%    1072325        stress-ng.time.voluntary_context_switches
     62132            +7.1%      66565 ±  4%  meminfo.PageTables
  48712422 ±  4%      +8.4%   52824690 ±  2%  cpuidle.C1E.time
  62293414 ±  2%      +9.0%   67917882 ±  3%  cpuidle.C6S.time
     68069 ±  2%      +9.6%      74599 ±  3%  cpuidle.C6S.usage


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-10-09  3:31 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=202610091149.c00cf9f2-lkp@intel.com \
    --to=yi1.lai@intel.com \
    --cc=aubrey.li@linux.intel.com \
    --cc=imv4bel@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=mingo@kernel.org \
    --cc=oe-lkp@lists.linux.dev \
    --cc=peterz@infradead.org \
    --cc=tim.c.chen@linux.intel.com \
    --cc=yu.c.chen@intel.com \
    --cc=zenghui.yu@linux.dev \
    /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.