From: kernel test robot <yi1.lai@intel.com>
To: quanyeyang via B4 Relay <devnull+quanyemostima.gmail.com@kernel.org>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
linux-crypto@vger.kernel.org, Thomas Graf <tgraf@suug.ch>,
Herbert Xu <herbert@gondor.apana.org.au>,
Andrew Morton <akpm@linux-foundation.org>,
NeilBrown <neilb@suse.com>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org,
syzbot+ef8d17bae14efb960935@syzkaller.appspotmail.com,
quanyeyang <quanyemostima@gmail.com>,
yi1.lai@intel.com
Subject: Re: [PATCH] rhashtable: use per-init-site lockdep classes for bucket locks
Date: Fri, 28 Aug 2026 08:54:49 +0800 [thread overview]
Message-ID: <202608280842.861e5949-lkp@intel.com> (raw)
In-Reply-To: <20260801-fix-rhashtable-bucket-lockdep-v1-1-15a0f8ae094c@gmail.com>
Hello,
kernel test robot noticed a 12.5% regression of stress-ng.shm-sysv.ops_per_sec on:
commit: 62d8460a4e7a3ee028e5134d86169001490e7a60 ("[PATCH] rhashtable: use per-init-site lockdep classes for bucket locks")
url: https://github.com/intel-lab-lkp/linux/commits/quanyeyang-via-B4-Relay/rhashtable-use-per-init-site-lockdep-classes-for-bucket-locks/20260815-014140
patch link: https://lore.kernel.org/all/20260801-fix-rhashtable-bucket-lockdep-v1-1-15a0f8ae094c@gmail.com/
patch subject: [PATCH] rhashtable: use per-init-site lockdep classes for bucket locks
testcase: stress-ng
config: x86_64-rhel-9.4
compiler: gcc-14
test machine: 224 threads 2 sockets Intel(R) Xeon(R) Platinum 8480CTDX (Sapphire Rapids) with 256G memory
parameters:
nr_threads: 100%
testtime: 60s
test: shm-sysv
cpufreq_governor: performance
If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <yi1.lai@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202608280842.861e5949-lkp@intel.com
Details are as below:
-------------------------------------------------------------------------------------------------->
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260828/202608280842.861e5949-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-r02/shm-sysv/stress-ng/60s
commit:
0131b508c0 ("Merge tag 'ntfs-for-7.2-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/linkinjeon/ntfs")
62d8460a4e ("[PATCH] rhashtable: use per-init-site lockdep classes for bucket locks")
0131b508c0e2489e 62d8460a4e7a3ee028e5134d861
---------------- ---------------------------
192413 +44.1% 277255 stress-ng.shm-sysv.nanosecs_per_shmat_call
349549 +24.2% 433996 stress-ng.shm-sysv.nanosecs_per_shmdt_call
174600 +51.9% 265191 stress-ng.shm-sysv.nanosecs_per_shmget_call
793610 -12.5% 694260 stress-ng.shm-sysv.ops
13236 -12.5% 11578 stress-ng.shm-sysv.ops_per_sec
65737 -10.0% 59167 ± 4% stress-ng.time.involuntary_context_switches
53645785 -12.0% 47213499 ± 2% stress-ng.time.minor_page_faults
4660 +24.6% 5806 stress-ng.time.percent_of_cpu_this_job_got
2585 +27.8% 3305 stress-ng.time.system_time
214.61 -14.7% 183.11 stress-ng.time.user_time
10735595 -7.0% 9986470 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
next prev parent reply other threads:[~2026-08-28 0:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 10:13 [PATCH] rhashtable: use per-init-site lockdep classes for bucket locks quanyeyang via B4 Relay
2026-08-01 10:13 ` quanyeyang
2026-08-01 11:12 ` NeilBrown
2026-08-02 10:33 ` Quanye Yang
2026-08-03 2:00 ` NeilBrown
2026-08-03 14:38 ` Quanye Yang
2026-08-14 19:27 ` kernel test robot
2026-08-28 0:54 ` kernel test robot [this message]
2026-08-29 11:50 ` Quanye Yang
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=202608280842.861e5949-lkp@intel.com \
--to=yi1.lai@intel.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=devnull+quanyemostima.gmail.com@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=neilb@suse.com \
--cc=oe-lkp@lists.linux.dev \
--cc=quanyemostima@gmail.com \
--cc=syzbot+ef8d17bae14efb960935@syzkaller.appspotmail.com \
--cc=tgraf@suug.ch \
/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.