From: Herbert Xu <herbert@gondor.apana.org.au>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: linux-crypto@vger.kernel.org, davem@davemloft.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] crypto: ccp - selective algorithm registration and ipsec-related fixes
Date: Sun, 9 Feb 2014 17:21:00 +0800 [thread overview]
Message-ID: <20140209092100.GD19429@gondor.apana.org.au> (raw)
In-Reply-To: <20140124221750.1894.48517.stgit@tlendack-t1.amdoffice.net>
On Fri, Jan 24, 2014 at 04:17:50PM -0600, Tom Lendacky wrote:
> 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.
All applied. Thanks!
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2014-02-09 9:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 22:17 Tom Lendacky
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 ` Herbert Xu [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=20140209092100.GD19429@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=davem@davemloft.net \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.lendacky@amd.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
all inboxes | Powered by JetHome®