From: kernel test robot <yi1.lai@intel.com>
To: Aaron Tomlin <atomlin@atomlin.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com, Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
yi1.lai@intel.com
Subject: [linux-next:master] [workqueue] a4d1cdc435: stress-ng.stack.ops_per_sec 18.5% improvement
Date: Wed, 16 Sep 2026 15:27:22 +0800 [thread overview]
Message-ID: <202609161514.be6a4fae-lkp@intel.com> (raw)
Hello,
kernel test robot noticed a 18.5% improvement of stress-ng.stack.ops_per_sec on:
commit: a4d1cdc4356de4325b0a9c6fb09afa6e121407b5 ("workqueue: Add workqueue_cpu_intensive tracepoint") https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.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: stack
cpufreq_governor: performance
Details are as below:
-------------------------------------------------------------------------------------------------->
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260916/202609161514.be6a4fae-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/stack/stress-ng/60s
commit:
ab85b68e63 ("workqueue: rename the pwq slot helpers shared with percpu")
a4d1cdc435 ("workqueue: Add workqueue_cpu_intensive tracepoint")
ab85b68e630e8a4d a4d1cdc4356de4325b0a9c6fb09
---------------- ---------------------------
%stddev %change %stddev
\ | \
2.09e+08 ± 2% +18.4% 2.475e+08 stress-ng.stack.ops
3493402 ± 2% +18.5% 4138262 stress-ng.stack.ops_per_sec
92.39 ± 3% +17.4% 108.49 stress-ng.time.user_time
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-16 7:27 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=202609161514.be6a4fae-lkp@intel.com \
--to=yi1.lai@intel.com \
--cc=atomlin@atomlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®