From: Oliver Sang <oliver.sang@intel.com>
To: Stephan Mueller <smueller@chronox.de>
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>
Subject: Re: [linux-next:master] [crypto] bb897c5504: stress-ng.af-alg.ops_per_sec -8.0% regression
Date: Sat, 10 Jun 2023 22:06:03 +0800 [thread overview]
Message-ID: <ZISDS6Ov7DS7Dis/@xsang-OptiPlex-9020> (raw)
In-Reply-To: <1697789.S9sCK8dtJg@tauon.chronox.de>
hi, Stephan,
On Fri, Jun 09, 2023 at 01:57:27PM +0200, Stephan Mueller wrote:
> 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.
got it. Thanks a lot for information!
>
> Ciao
> Stephan
>
>
prev parent reply other threads:[~2023-06-10 14:06 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
2023-06-10 14:06 ` Oliver Sang [this message]
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=ZISDS6Ov7DS7Dis/@xsang-OptiPlex-9020 \
--to=oliver.sang@intel.com \
--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=smueller@chronox.de \
--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