From: Stephan Mueller <smueller@chronox.de>
To: kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
Linux Memory Management List <linux-mm@kvack.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
linux-crypto@vger.kernel.org, ying.huang@intel.com,
feng.tang@intel.com, fengwei.yin@intel.com,
oliver.sang@intel.com
Subject: Re: [linux-next:master] [crypto] bb897c5504: stress-ng.af-alg.ops_per_sec -8.0% regression
Date: Fri, 09 Jun 2023 13:57:27 +0200 [thread overview]
Message-ID: <1697789.S9sCK8dtJg@tauon.chronox.de> (raw)
In-Reply-To: <202306081658.d5c86ae9-oliver.sang@intel.com>
Am Freitag, 9. Juni 2023, 10:02:32 CEST schrieb kernel test robot:
Hi,
> Hello,
>
> kernel test robot noticed a -8.0% regression of stress-ng.af-alg.ops_per_sec
> on:
>
>
> commit: bb897c55042e9330bcf88b4b13cbdd6f9fabdd5e ("crypto: jitter - replace
> LFSR with SHA3-256")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
>
> testcase: stress-ng
> test machine: 36 threads 1 sockets Intel(R) Core(TM) i9-10980XE CPU @
> 3.00GHz (Cascade Lake) with 128G memory parameters:
Thank you for the report, but this change in performance is expected to ensure
proper entropy collection. I assume that the jitterentropy_rng is queried via
AF_ALG. Considering that the amount of data to be generated (and thus the
effect of the performance degradation) is small, there should be no noticeable
impact on users.
Ciao
Stephan
next prev parent reply other threads:[~2023-06-09 11:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 8:02 kernel test robot
2023-06-09 11:57 ` Stephan Mueller [this message]
2023-06-10 14:06 ` Oliver Sang
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=1697789.S9sCK8dtJg@tauon.chronox.de \
--to=smueller@chronox.de \
--cc=feng.tang@intel.com \
--cc=fengwei.yin@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=ying.huang@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