From: Leonidas Da Silva Barbosa <leosilva@linux.vnet.ibm.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: mhcerri@linux.vnet.ibm.com, fin@linux.vnet.ibm.com
Subject: [PATCH 0/8] NX crypto driver reestructure
Date: Thu, 24 Jul 2014 10:44:18 -0300 [thread overview]
Message-ID: <20140724134414.GA22921@bluepex.com> (raw)
This set of patches deals with the reescruture of NX driver replacing the
use of spinlocks, that assure crypto context concurrency, by a copy of crypto
ctx to another region of memory in order to be used by the current algorithm.
As this region of memory tends to be used constantly also was added a kmemcache
chunk avoiding the cost of constant allocations.
Leonidas Da Silva Barbosa (8):
Adding nx_copy_ctx and kmemcache to handle with crypto context
Replacing spinlocks by nx_copy_ctx on NX-AES-CBC
Replacing spinlocks by nx_copy_ctx on NX-AES-CCM
Replacing spinlocks by nx_copy_ctx on NX-AES-CTR
Replacing spinlocks by nx_copy_ctx on NX-AES-ECB
Replacing spinlocks by nx_copy_ctx on NX-AES-GCM
Replacing spinlocks by nx_copy_ctx on NX-AES-XCBC
Replacing spinlocks by nx_copy_ctx on NX-SHA256 and NX-SHA512
drivers/crypto/nx/nx-aes-cbc.c | 20 +++++++----
drivers/crypto/nx/nx-aes-ccm.c | 42 ++++++++++++++---------
drivers/crypto/nx/nx-aes-ctr.c | 20 +++++++----
drivers/crypto/nx/nx-aes-ecb.c | 20 +++++++----
drivers/crypto/nx/nx-aes-gcm.c | 64 +++++++++++++++++++----------------
drivers/crypto/nx/nx-aes-xcbc.c | 51 ++++++++++++++++------------
drivers/crypto/nx/nx-sha256.c | 70 ++++++++++++++++++++++++---------------
drivers/crypto/nx/nx-sha512.c | 70 ++++++++++++++++++++++++---------------
drivers/crypto/nx/nx.c | 45 ++++++++++++++++++++++++-
drivers/crypto/nx/nx.h | 8 +++--
10 files changed, 259 insertions(+), 151 deletions(-)
reply other threads:[~2014-07-24 13:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140724134414.GA22921@bluepex.com \
--to=leosilva@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=fin@linux.vnet.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhcerri@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).