From: kernel test robot <oliver.sang@intel.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Chris Mason <clm@meta.com>, <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"Thomas Gleixner" <tglx@linutronix.de>, <oliver.sang@intel.com>
Subject: Re: [PATCH] futex: Temporary disable FUTEX_PRIVATE_HASH
Date: Wed, 16 Jul 2025 09:34:24 +0800 [thread overview]
Message-ID: <202507160223.2a483e8b-lkp@intel.com> (raw)
In-Reply-To: <20250630145034.8JnINEaS@linutronix.de>
Hello,
from the commit message, we know this 'temporary disable' is to address a
performance regression. so we still send out this report FYI what's the
possible performance impact. however, our team focus on micro benchmark,
so, anyway, just FYI.
kernel test robot noticed a 1.9% improvement of perf-bench-futex.ops/s on:
commit: bc1aa469e545fe16a62d501e095630cccc3fe1c4 ("[PATCH] futex: Temporary disable FUTEX_PRIVATE_HASH")
url: https://github.com/intel-lab-lkp/linux/commits/Sebastian-Andrzej-Siewior/futex-Temporary-disable-FUTEX_PRIVATE_HASH/20250630-225317
base: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git d0b3b7b22dfa1f4b515fd3a295b3fd958f9e81af
patch link: https://lore.kernel.org/all/20250630145034.8JnINEaS@linutronix.de/
patch subject: [PATCH] futex: Temporary disable FUTEX_PRIVATE_HASH
testcase: perf-bench-futex
config: x86_64-rhel-9.4
compiler: gcc-12
test machine: 192 threads 2 sockets Intel(R) Xeon(R) 6740E CPU @ 2.4GHz (Sierra Forest) with 256G memory
parameters:
runtime: 300s
nr_task: 100%
test: hash
shared: shared
cpufreq_governor: performance
Details are as below:
-------------------------------------------------------------------------------------------------->
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250716/202507160223.2a483e8b-lkp@intel.com
=========================================================================================
compiler/cpufreq_governor/kconfig/nr_task/rootfs/runtime/shared/tbox_group/test/testcase:
gcc-12/performance/x86_64-rhel-9.4/100%/debian-12-x86_64-20240206.cgz/300s/shared/lkp-srf-2sp2/hash/perf-bench-futex
commit:
v6.16-rc4
bc1aa469e5 ("futex: Temporary disable FUTEX_PRIVATE_HASH")
v6.16-rc4 bc1aa469e545fe16a62d501e095
---------------- ---------------------------
%stddev %change %stddev
\ | \
2249734 +1.9% 2291792 perf-bench-futex.ops/s
6622 +3.7% 6868 perf-bench-futex.time.user_time
115.83 ± 12% +40.1% 162.33 ± 18% perf-sched.wait_and_delay.count.irqentry_exit_to_user_mode.asm_sysvec_call_function_single.[unknown].[unknown]
4.40 ± 19% +343.0% 19.51 ± 64% perf-sched.wait_and_delay.max.ms.schedule_timeout.__wait_for_common.wait_for_completion_state.kernel_clone
4.15 ± 17% +347.3% 18.55 ± 69% perf-sched.wait_time.max.ms.schedule_timeout.__wait_for_common.wait_for_completion_state.kernel_clone
21.00 ± 63% +121.4% 46.50 ± 11% perf-c2c.DRAM.local
4129 ± 57% +225.5% 13444 perf-c2c.DRAM.remote
67558 ± 56% +66.3% 112351 perf-c2c.HITM.local
4045 ± 57% +227.2% 13237 perf-c2c.HITM.remote
71603 ± 57% +75.4% 125588 perf-c2c.HITM.total
1.674e+08 ± 20% +19.0% 1.991e+08 perf-stat.i.cache-misses
4.096e+08 ± 20% +19.4% 4.891e+08 perf-stat.i.cache-references
0.36 +2.9% 0.37 perf-stat.overall.MPKI
3127 -1.8% 3070 perf-stat.overall.cycles-between-cache-misses
1.669e+08 ± 20% +18.9% 1.985e+08 perf-stat.ps.cache-misses
4.085e+08 ± 20% +19.3% 4.874e+08 perf-stat.ps.cache-references
1.622e+14 -1.0% 1.606e+14 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
next prev parent reply other threads:[~2025-07-16 1:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 19:00 futex performance regression from "futex: Allow automatic allocation of process wide futex hash" Chris Mason
2025-06-04 9:28 ` Sebastian Andrzej Siewior
2025-06-04 15:48 ` Chris Mason
2025-06-04 20:08 ` Sebastian Andrzej Siewior
2025-06-06 0:55 ` Chris Mason
2025-06-06 7:06 ` Sebastian Andrzej Siewior
2025-06-06 21:06 ` Chris Mason
2025-06-06 22:17 ` Chris Mason
2025-06-24 19:01 ` Peter Zijlstra
2025-06-26 11:01 ` Chris Mason
2025-06-26 13:17 ` Peter Zijlstra
2025-06-26 13:50 ` Sebastian Andrzej Siewior
2025-06-27 11:04 ` Peter Zijlstra
2025-06-27 12:14 ` Sebastian Andrzej Siewior
2025-06-30 14:50 ` [PATCH] futex: Temporary disable FUTEX_PRIVATE_HASH Sebastian Andrzej Siewior
2025-07-01 13:13 ` [tip: locking/urgent] " tip-bot2 for Sebastian Andrzej Siewior
2025-07-16 1:34 ` kernel test robot [this message]
2025-06-26 13:48 ` futex performance regression from "futex: Allow automatic allocation of process wide futex hash" Sebastian Andrzej Siewior
2025-06-26 14:36 ` Peter Zijlstra
2025-06-27 12:24 ` Sebastian Andrzej Siewior
2025-06-27 22:48 ` Tim Chen
2025-06-28 8:23 ` Peter Zijlstra
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=202507160223.2a483e8b-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=bigeasy@linutronix.de \
--cc=clm@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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®