From: Tadeusz Struk <tadeusz.struk@intel.com>
To: Stephan Mueller <smueller@chronox.de>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
linux-crypto@vger.kernel.org, qat-linux@intel.com
Subject: Re: [PATCH RESEND 0/2] crypto: algif - change algif_skcipher to be asynchronous
Date: Mon, 09 Mar 2015 15:10:46 +0000 [thread overview]
Message-ID: <54FDB7F6.10004@intel.com> (raw)
In-Reply-To: <2623212.v9KkTj4KSQ@tachyon.chronox.de>
Hi Stephan,
On 03/08/2015 11:20 AM, Stephan Mueller wrote:
> As you may know, I am working on libkcapi [1] to cover the user space AF_ALG
> interface and provide an easy-to use interface for applications.
>
> I am now trying to cover your interface proposal there and also measure the
> speed of it. What bothers me currently is the following: how would I be able
> to detect whether the implemented support is available in the current kernel?
You don't need to detect that. You can just use the new interface, and in the older
kernels without AIO support in skcipher it will seamlessly fallback to the synchronous interface.
The only problem is that the socket layer didn't like asynch operations before commit
06539d3071067ff146a9bffd1c801fa56d290909.
The way it can be tackled for the older kernels is the distros will need update their kernels
with the mentioned commit. They should do it anyway because it looks like that was a bug.
One other thing to keep in mind is - to be able to see the benefit of AIO you need to use
some encryption offload engine, where you can asynchronously offload multiple operations.
With my dh895xxcc engine I see around 8x throughput improvement.
Regards,
Tadeusz
prev parent reply other threads:[~2015-03-09 15:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 19:35 [PATCH RESEND 0/2] crypto: algif - change algif_skcipher to be asynchronous Tadeusz Struk
2015-02-27 19:35 ` [PATCH RESEND 1/2] crypto: af_alg - Allow to link sgl Tadeusz Struk
2015-02-27 19:35 ` [PATCH RESEND 2/2] crypto: algif - change algif_skcipher to be asynchronous Tadeusz Struk
2015-03-06 11:44 ` Herbert Xu
2015-03-06 12:04 ` Tadeusz Struk
2015-03-06 12:09 ` Herbert Xu
2015-03-09 20:06 ` Tadeusz Struk
2015-03-08 11:20 ` [PATCH RESEND 0/2] " Stephan Mueller
2015-03-09 15:10 ` Tadeusz Struk [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=54FDB7F6.10004@intel.com \
--to=tadeusz.struk@intel.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=qat-linux@intel.com \
--cc=smueller@chronox.de \
/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).