From: Tadeusz Struk <tadeusz.struk@intel.com>
To: herbert@gondor.apana.org.au
Cc: davem@davemloft.net, linux-crypto@vger.kernel.org, qat-linux@intel.com
Subject: [PATCH RESEND 0/2] crypto: algif - change algif_skcipher to be asynchronous
Date: Fri, 27 Feb 2015 11:35:38 -0800 [thread overview]
Message-ID: <20150227193538.10553.6144.stgit@tstruk-mobl1> (raw)
The way the algif_skcipher works currently is that on sendmsg/sendpage it
builds an sgl for the input data and then on read/recvmsg it sends the job
for encryption putting the user to sleep till the data is processed.
This way it can only handle one job at a given time.
To be able to fuly utilize the potential of existing crypto hardware
accelerators it is required to submit multiple jobs in asynchronously.
This series adds support for asynchronous operations for algif_skcipher.
First patch enables af_alg sgl to be linked.
Second patch implement asynch read for skcipher.
Resend with updates for 4.0
Signed-off-by: Tadeusz Struk <tadeusz.struk@intel.com>
---
Tadeusz Struk (2):
crypto: af_alg - Allow to link sgl
crypto: algif - change algif_skcipher to be asynchronous
crypto/af_alg.c | 18 ++-
crypto/algif_skcipher.c | 308 ++++++++++++++++++++++++++++++++++++++++++++++-
include/crypto/if_alg.h | 4 -
3 files changed, 317 insertions(+), 13 deletions(-)
next reply other threads:[~2015-02-27 19:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 19:35 Tadeusz Struk [this message]
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
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=20150227193538.10553.6144.stgit@tstruk-mobl1 \
--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 \
/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