From: kernel test robot <yi1.lai@intel.com>
To: Puranjay Mohan <puranjay@kernel.org>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org,
"Paul E. McKenney" <paulmck@kernel.org>,
rcu@vger.kernel.org, yi1.lai@intel.com
Subject: [linus:master] [rcu] ec5ee5417b: stress-ng.ramfs.ops_per_sec 25.7% improvement
Date: Thu, 24 Sep 2026 19:33:08 +0800 [thread overview]
Message-ID: <202609241934.228b4a14-lkp@intel.com> (raw)
Hello,
kernel test robot noticed a 25.7% improvement of stress-ng.ramfs.ops_per_sec on:
commit: ec5ee5417b00278fa050b38d878b76f1365420fb ("rcu: Advance callbacks for expedited GP completion in rcu_core()") 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 Intel(R) Xeon(R) 6768P CPU @ 2.4GHz (Granite Rapids) with 64G memory
parameters:
nr_threads: 100%
testtime: 60s
test: ramfs
cpufreq_governor: performance
Details are as below:
-------------------------------------------------------------------------------------------------->
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260924/202609241934.228b4a14-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-gnr-2sp4/ramfs/stress-ng/60s
commit:
fde2b18817 ("rcu: Detect expedited grace period completion in rcu_pending()")
ec5ee5417b ("rcu: Advance callbacks for expedited GP completion in rcu_core()")
fde2b18817e4f32b ec5ee5417b00278fa050b38d878
---------------- ---------------------------
%stddev %change %stddev
\ | \
427110 +25.7% 537009 stress-ng.ramfs.ops
7124 +25.7% 8957 stress-ng.ramfs.ops_per_sec
6004 ± 2% +561.7% 39731 stress-ng.time.involuntary_context_switches
685.50 -5.1% 650.33 stress-ng.time.percent_of_cpu_this_job_got
405.23 -5.4% 383.53 stress-ng.time.system_time
776758 +19.9% 931227 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-09-24 11:33 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=202609241934.228b4a14-lkp@intel.com \
--to=yi1.lai@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=paulmck@kernel.org \
--cc=puranjay@kernel.org \
--cc=rcu@vger.kernel.org \
/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.