From: Herbert Xu <herbert@gondor.apana.org.au>
To: Yang Shen <shenyang39@huawei.com>
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org, gregkh@linuxfoundation.org
Subject: Re: [RFC PATCH 0/6] crypto: benchmark - add the crypto benchmark
Date: Fri, 14 Oct 2022 16:25:57 +0800 [thread overview]
Message-ID: <Y0kdFaXQtsJxgrC0@gondor.apana.org.au> (raw)
In-Reply-To: <09d0686b-1955-c63d-c02d-fb0d2db42672@huawei.com>
On Fri, Oct 14, 2022 at 09:43:40AM +0800, Yang Shen wrote:
>
> Got it. I'll try to support this on the tcrypt.
Before you get too far into this, please note that I have no
preference as to whether you go with tcrypt or your new benchmark
code.
My only requirement is that we pick one mechanism.
But obivously others might have a preference so you should try
to produce RFCs as early as possible.
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2022-10-14 8:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 12:05 [RFC PATCH 0/6] crypto: benchmark - add the crypto benchmark Yang Shen
2022-09-19 12:05 ` [RFC PATCH 1/6] moduleparams: Add hexulong type parameter Yang Shen
2022-09-19 12:05 ` [RFC PATCH 2/6] crypto: benchmark - add a crypto benchmark tool Yang Shen
2022-09-20 7:31 ` Greg KH
2022-09-21 8:20 ` Yang Shen
2022-09-19 12:05 ` [RFC PATCH 3/6] crytpo: benchmark - support compression/decompresssion Yang Shen
2022-09-19 12:05 ` [RFC PATCH 4/6] crypto: benchmark - add help information Yang Shen
2022-09-19 12:05 ` [RFC PATCH 5/6] crypto: benchmark - add API documentation Yang Shen
2022-09-19 12:05 ` [RFC PATCH 6/6] MAINTAINERS: add crypto benchmark MAINTAINER Yang Shen
2022-09-20 8:28 ` [RFC PATCH 0/6] crypto: benchmark - add the crypto benchmark Herbert Xu
2022-09-21 8:19 ` Yang Shen
2022-09-30 4:51 ` Herbert Xu
2022-10-14 1:43 ` Yang Shen
2022-10-14 8:25 ` Herbert Xu [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=Y0kdFaXQtsJxgrC0@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shenyang39@huawei.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