From: kernel test robot <oliver.sang@intel.com>
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>,
Christian Brauner <brauner@kernel.org>, <oliver.sang@intel.com>
Subject: [linus:master] [ns] c0aac5975b: stress-ng.bind-mount.ops_per_sec 5.0% improvement
Date: Fri, 27 Feb 2026 15:41:59 +0800 [thread overview]
Message-ID: <202602271512.37537e7e-lkp@intel.com> (raw)
Hello,
kernel test robot noticed a 5.0% improvement of stress-ng.bind-mount.ops_per_sec on:
commit: c0aac5975bafc86f6817b14e9f71dcb5064a9183 ("ns: pad refcount")
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: 64 threads 2 sockets Intel(R) Xeon(R) Gold 6346 CPU @ 3.10GHz (Ice Lake) with 256G memory
parameters:
nr_threads: 100%
disk: 1HDD
testtime: 60s
fs: xfs
test: bind-mount
cpufreq_governor: performance
Details are as below:
-------------------------------------------------------------------------------------------------->
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260227/202602271512.37537e7e-lkp@intel.com
=========================================================================================
compiler/cpufreq_governor/disk/fs/kconfig/nr_threads/rootfs/tbox_group/test/testcase/testtime:
gcc-14/performance/1HDD/xfs/x86_64-rhel-9.4/100%/debian-13-x86_64-20250902.cgz/lkp-icl-2sp8/bind-mount/stress-ng/60s
commit:
887e97745e ("fs: track the inode having file locks with a flag in ->i_opflags")
c0aac5975b ("ns: pad refcount")
887e97745ec336c2 c0aac5975bafc86f6817b14e9f7
---------------- ---------------------------
%stddev %change %stddev
\ | \
2345 -3.9% 2254 stress-ng.bind-mount.microsecs_per_mount
3070 -5.5% 2902 stress-ng.bind-mount.microsecs_per_umount
704181 +4.9% 739032 stress-ng.bind-mount.ops
11736 +5.0% 12318 stress-ng.bind-mount.ops_per_sec
10287 +6.3% 10937 ± 3% stress-ng.time.involuntary_context_switches
1810201 +4.6% 1893350 stress-ng.time.voluntary_context_switches
1.54 +0.1 1.62 mpstat.cpu.all.soft%
157837 +5.0% 165680 vmstat.system.cs
179327 +3.9% 186257 vmstat.system.in
2.772e+09 +3.3% 2.863e+09 ± 2% perf-stat.i.branch-instructions
64587234 +2.2% 65980821 perf-stat.i.cache-references
163281 +5.0% 171502 perf-stat.i.context-switches
1.305e+10 +3.4% 1.35e+10 ± 2% perf-stat.i.instructions
0.45 +2.6% 0.46 perf-stat.i.ipc
2.48 +5.1% 2.61 perf-stat.i.metric.K/sec
2.728e+09 +3.3% 2.818e+09 ± 2% perf-stat.ps.branch-instructions
63500861 +2.2% 64868461 perf-stat.ps.cache-references
160406 +5.0% 168462 perf-stat.ps.context-switches
1.285e+10 +3.4% 1.329e+10 ± 2% perf-stat.ps.instructions
7.871e+11 +3.5% 8.143e+11 ± 2% perf-stat.total.instructions
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-02-27 7:42 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=202602271512.37537e7e-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mjguzik@gmail.com \
--cc=oe-lkp@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox