From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH] crypto: extend hash benchmark to cover more algorithms
Date: Wed, 6 May 2020 09:29:34 -0500 [thread overview]
Message-ID: <022aca11-86d0-3603-8eca-99f16d131011@redhat.com> (raw)
In-Reply-To: <20200506135104.1080162-1-berrange@redhat.com>
On 5/6/20 8:51 AM, Daniel P. Berrangé wrote:
> Extend the hash benchmark so that it can validate all algorithms
> supported by QEMU instead of being limited to sha256.
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> tests/benchmark-crypto-hash.c | 73 ++++++++++++++++++++++++++++-------
> 1 file changed, 59 insertions(+), 14 deletions(-)
>
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2020-05-06 14:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 13:51 [PATCH] crypto: extend hash benchmark to cover more algorithms Daniel P. Berrangé
2020-05-06 14:29 ` Eric Blake [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-27 10:11 Daniel P. Berrangé
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=022aca11-86d0-3603-8eca-99f16d131011@redhat.com \
--to=eblake@redhat.com \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).