From: Tom Lendacky <thomas.lendacky@amd.com>
To: <linux-crypto@vger.kernel.org>, <herbert@gondor.apana.org.au>,
<davem@davemloft.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/4] crypto: ccp - selective algorithm registration and ipsec-related fixes
Date: Fri, 24 Jan 2014 16:17:50 -0600 [thread overview]
Message-ID: <20140124221750.1894.48517.stgit@tlendack-t1.amdoffice.net> (raw)
Patch 1: Allow for selectively disabling the registration of an algorithm
family (sha or aes algorithms) via module parameters.
Patch 2-4: Fix errors/issues that were found during IPSec testing. In
order to prevent deadlocks with the networking code, the crypto callback
was changed to run as a tasklet. In order for the callback to be run as
a tasklet, the HMAC calculation needed to be moved out of the callback
path (since it sleeps) and into the CCP sha operation logic. Additionally,
trying to allow concurrency within the tfm while maintaining serialization
of the tfm per CPU was not working properly so a single queue is used now.
This patch series is based on the cryptodev-2.6 kernel tree.
---
Tom Lendacky (4):
crypto: ccp - Allow for selective disablement of crypto API algorithms
crypto: ccp - Move HMAC calculation down to ccp ops file
crypto: ccp - Use a single queue for proper ordering of tfm requests
crypto: ccp - Perform completion callbacks using a tasklet
drivers/crypto/ccp/ccp-crypto-main.c | 201 ++++++++++++----------------------
drivers/crypto/ccp/ccp-crypto-sha.c | 130 ++++------------------
drivers/crypto/ccp/ccp-crypto.h | 8 +
drivers/crypto/ccp/ccp-dev.c | 21 +++-
drivers/crypto/ccp/ccp-ops.c | 104 +++++++++++++++++-
include/linux/ccp.h | 7 +
6 files changed, 229 insertions(+), 242 deletions(-)
--
Tom Lendacky
next reply other threads:[~2014-01-24 22:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 22:17 Tom Lendacky [this message]
2014-01-24 22:17 ` [PATCH 1/4] crypto: ccp - Allow for selective disablement of crypto API algorithms Tom Lendacky
2014-01-24 22:18 ` [PATCH 2/4] crypto: ccp - Move HMAC calculation down to ccp ops file Tom Lendacky
2014-01-24 22:18 ` [PATCH 3/4] crypto: ccp - Use a single queue for proper ordering of tfm requests Tom Lendacky
2014-01-24 22:18 ` [PATCH 4/4] crypto: ccp - Perform completion callbacks using a tasklet Tom Lendacky
2014-02-09 9:21 ` [PATCH 0/4] crypto: ccp - selective algorithm registration and ipsec-related fixes 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=20140124221750.1894.48517.stgit@tlendack-t1.amdoffice.net \
--to=thomas.lendacky@amd.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®