From: Cristian Stoica <cristian.stoica@freescale.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: <linux-crypto@vger.kernel.org>, <davem@davemloft.net>
Subject: Re: [PATCH] crypto: tcrypt speed: fix filter for aead algorithms
Date: Fri, 27 Feb 2015 13:14:20 +0200 [thread overview]
Message-ID: <54F0518C.1040801@freescale.com> (raw)
In-Reply-To: <20150227092503.GA27831@gondor.apana.org.au>
Hi Herbert,
On 02/27/2015 11:25 AM, Herbert Xu wrote:
> On Tue, Feb 03, 2015 at 03:59:48PM +0200, Cristian Stoica wrote:
>> test_aead_speed is written for sync algorithms without specifically
[...]
> Please fix it to test asynchronously instead.
Thanks for review.
I think that a fix for async aead requires a different test function as
is the case with test_cipher_speed/test_acipher_speed and also with
test_hash_speed/test_ahash_speed.
But I see a issue here with the current async tests:
int test_acipher_cycles(...)
{
for (i = 0; i < 8; i++) {
[...]
ret = do_one_acipher_op(req, crypto_ablkcipher_encrypt(req));
[...]
}
}
and in do_one_acipher_op we wait for completion of
crypto_ablkcipher_encrypt:
if (ret == -EINPROGRESS || ret == -EBUSY) {
struct tcrypt_result *tr = req->base.data;
ret = wait_for_completion_interruptible(&tr->completion);
}
Doesn't this defeat the purpose of async execution?
Cristian S.
next prev parent reply other threads:[~2015-02-27 11:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 13:59 [PATCH] crypto: tcrypt speed: fix filter for aead algorithms Cristian Stoica
2015-02-27 9:25 ` Herbert Xu
2015-02-27 11:14 ` Cristian Stoica [this message]
2015-02-28 9:13 ` Herbert Xu
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=54F0518C.1040801@freescale.com \
--to=cristian.stoica@freescale.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.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).