From: Tejun Heo <tj@kernel.org>
To: kernel test robot <oliver.sang@intel.com>
Cc: Breno Leitao <leitao@debian.org>,
oe-lkp@lists.linux.dev, lkp@intel.com,
linux-crypto@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
netdev@vger.kernel.org
Subject: Re: [herbert-cryptodev-2.6:master] [rhashtable] e1d3422c95: stress-ng.syscall.ops_per_sec 98.9% regression
Date: Sun, 29 Dec 2024 12:54:47 -1000 [thread overview]
Message-ID: <Z3HTN1gvVE9tfa4Y@slm.duckdns.org> (raw)
In-Reply-To: <202412271017.cad7675-lkp@intel.com>
On Fri, Dec 27, 2024 at 11:10:11AM +0800, kernel test robot wrote:
>
>
> Hello,
>
> kernel test robot noticed a 98.9% regression of stress-ng.syscall.ops_per_sec on:
>
>
> commit: e1d3422c95f003eba241c176adfe593c33e8a8f6 ("rhashtable: Fix potential deadlock by moving schedule_work outside lock")
> https://git.kernel.org/cgit/linux/kernel/git/herbert/cryptodev-2.6.git master
>
> testcase: stress-ng
> config: x86_64-rhel-9.4
> compiler: gcc-12
> test machine: 224 threads 2 sockets Intel(R) Xeon(R) Platinum 8480CTDX (Sapphire Rapids) with 256G memory
> parameters:
>
> nr_threads: 100%
> testtime: 60s
> test: syscall
> cpufreq_governor: performance
Hmm... the only meaningful behavior difference would be that after the
patch, rht_grow_above_75() test is done regardless of the return value while
before it was done only when the return value is zero. Breno, can you please
look into whether this report is valid and whether restoring the NULL check
makes it go away?
Thanks.
--
tejun
next prev parent reply other threads:[~2024-12-29 22:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-27 3:10 [herbert-cryptodev-2.6:master] [rhashtable] e1d3422c95: stress-ng.syscall.ops_per_sec 98.9% regression kernel test robot
2024-12-29 22:54 ` Tejun Heo [this message]
2025-01-02 1:10 ` Herbert Xu
2025-01-02 15:45 ` Breno Leitao
2025-01-03 13:41 ` Breno Leitao
2025-01-07 6:35 ` Oliver Sang
2025-01-08 12:20 ` Breno Leitao
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=Z3HTN1gvVE9tfa4Y@slm.duckdns.org \
--to=tj@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=leitao@debian.org \
--cc=linux-crypto@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
/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