From: Tadeusz Struk <tadeusz.struk@intel.com>
To: herbert@gondor.apana.org.au
Cc: linux-crypto@vger.kernel.org, netdev@vger.kernel.org,
davem@davemloft.net, qat-linux@intel.com,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] crypto: algif - change algif_skcipher to be asynchronous
Date: Thu, 29 Jan 2015 15:13:39 -0800 [thread overview]
Message-ID: <20150129231338.25156.65450.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.
First patch enables asynchronous read and write on socket.
Second patch enables af_alg sgl to be linked.
Third patch implement asynch read for skcipher.
Signed-off-by: Tadeusz Struk <tadeusz.struk@intel.com>
---
Tadeusz Struk (3):
net: socket: enable async read and write
crypto: af_alg - Allow to link sgl
crypto: algif - change algif_skcipher to be asynchronous
crypto/af_alg.c | 16 ++
crypto/algif_skcipher.c | 315 ++++++++++++++++++++++++++++++++++++++++++++++-
include/crypto/if_alg.h | 4 -
include/net/sock.h | 2
net/socket.c | 48 ++++++-
5 files changed, 364 insertions(+), 21 deletions(-)
next reply other threads:[~2015-01-29 23:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 23:13 Tadeusz Struk [this message]
2015-01-29 23:13 ` [PATCH 1/3] net: socket: enable async read and write Tadeusz Struk
2015-01-30 18:30 ` Tadeusz Struk
2015-01-29 23:13 ` [PATCH 2/3] crypto: af_alg - Allow to link sgl Tadeusz Struk
2015-01-29 23:13 ` [PATCH 3/3] crypto: algif - change algif_skcipher to be asynchronous Tadeusz Struk
2015-02-01 18:31 ` [PATCH 0/3] " Stephan Mueller
2015-02-02 15:03 ` Tadeusz Struk
2015-02-02 16:40 ` Stephan Mueller
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=20150129231338.25156.65450.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=linux-kernel@vger.kernel.org \
--cc=netdev@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