From: kernel test robot <yi1.lai@intel.com>
To: "Jérémy Jean" <Jeremy.Jean@oss.cyber.gouv.fr>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org,
Christian Brauner <brauner@kernel.org>,
yi1.lai@intel.com
Subject: [linus:master] [nsfs] 82e9343260: stress-ng.usersyscall.ops_per_sec 12.4% improvement
Date: Wed, 14 Oct 2026 15:02:43 +0800 [thread overview]
Message-ID: <202610140836.4d5baee2-lkp@intel.com> (raw)
Hello,
kernel test robot noticed a 12.4% improvement of stress-ng.usersyscall.ops_per_sec on:
commit: 82e9343260dfc6dda6349f285d9a5eac3e0738d7 ("nsfs: keep namespace tree fields stable until after RCU grace period") 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: 224 threads 2 sockets Intel(R) Xeon(R) (Sapphire Rapids) with 128G memory
parameters:
nr_threads: 100%
testtime: 60s
test: usersyscall
cpufreq_governor: performance
Details are as below:
-------------------------------------------------------------------------------------------------->
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20261014/202610140836.4d5baee2-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-2sp2/usersyscall/stress-ng/60s
commit:
0ecd56573c ("ext4: Avoid entering writeback paths during fastcommit replay")
82e9343260 ("nsfs: keep namespace tree fields stable until after RCU grace period")
0ecd56573c1f272c 82e9343260dfc6dda6349f285d9
---------------- ---------------------------
%stddev %change %stddev
\ | \
33817 -10.8% 30152 stress-ng.usersyscall.nanosecs_per_syscall
1.908e+08 +12.4% 2.144e+08 stress-ng.usersyscall.ops
3187687 +12.4% 3582876 stress-ng.usersyscall.ops_per_sec
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-14 7:02 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=202610140836.4d5baee2-lkp@intel.com \
--to=yi1.lai@intel.com \
--cc=Jeremy.Jean@oss.cyber.gouv.fr \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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 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.