From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH 1/4] tests: allow filtering crypto cipher benchmark tests
Date: Fri, 25 Oct 2019 15:24:55 +0200 [thread overview]
Message-ID: <e54bbedb-8f6f-695f-bb38-df7b808d0f37@redhat.com> (raw)
In-Reply-To: <20191017145654.11371-2-berrange@redhat.com>
On 10/17/19 4:56 PM, Daniel P. Berrangé wrote:
> Add support for specifying a cipher mode and chunk size as argv to
> filter which combinations are benchmarked. For example to only
> benchmark XTS mode with 512 byte chunks:
>
> ./tests/benchmark-crypto-cipher xts 512
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> tests/benchmark-crypto-cipher.c | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/tests/benchmark-crypto-cipher.c b/tests/benchmark-crypto-cipher.c
> index 67fdf8c31d..3ca31a2779 100644
> --- a/tests/benchmark-crypto-cipher.c
> +++ b/tests/benchmark-crypto-cipher.c
> @@ -161,15 +161,26 @@ static void test_cipher_speed_xts_aes_256(const void *opaque)
>
> int main(int argc, char **argv)
> {
> + char *alg = NULL;
> + char *size = NULL;
> g_test_init(&argc, &argv, NULL);
> g_assert(qcrypto_init(NULL) == 0);
>
> #define ADD_TEST(mode, cipher, keysize, chunk) \
> - g_test_add_data_func( \
> + if ((!alg || g_str_equal(alg, #mode)) && \
> + (!size || g_str_equal(size, #chunk))) \
> + g_test_add_data_func( \
> "/crypto/cipher/" #mode "-" #cipher "-" #keysize "/chunk-" #chunk, \
> (void *)chunk, \
> test_cipher_speed_ ## mode ## _ ## cipher ## _ ## keysize)
>
> + if (argc >= 2) {
> + alg = argv[1];
> + }
> + if (argc >= 3) {
> + size = argv[2];
> + }
> +
> #define ADD_TESTS(chunk) \
> do { \
> ADD_TEST(ecb, aes, 128, chunk); \
>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
next prev parent reply other threads:[~2019-10-25 13:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 14:56 [PATCH 0/4] crypto: improve performance of ciphers in XTS mode Daniel P. Berrangé
2019-10-17 14:56 ` [PATCH 1/4] tests: allow filtering crypto cipher benchmark tests Daniel P. Berrangé
2019-10-25 13:24 ` Philippe Mathieu-Daudé [this message]
2019-10-25 13:45 ` Stefano Garzarella
2019-10-17 14:56 ` [PATCH 2/4] tests: benchmark crypto with fixed data size, not time period Daniel P. Berrangé
2019-10-25 13:36 ` Philippe Mathieu-Daudé
2019-10-25 13:46 ` Stefano Garzarella
2019-10-17 14:56 ` [PATCH 3/4] crypto: add support for gcrypt's native XTS impl Daniel P. Berrangé
2019-10-25 13:31 ` Philippe Mathieu-Daudé
2019-10-25 14:03 ` Stefano Garzarella
2019-10-17 14:56 ` [PATCH 4/4] crypto: add support for nettle's " Daniel P. Berrangé
2019-10-25 13:33 ` Philippe Mathieu-Daudé
2019-10-25 14:13 ` Stefano Garzarella
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=e54bbedb-8f6f-695f-bb38-df7b808d0f37@redhat.com \
--to=philmd@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).