public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Megha Dey <megha.dey@intel.com>
To: herbert@gondor.apana.org.au
Cc: tim.c.chen@linux.intel.com, davem@davemloft.net,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	megha.dey@intel.com, fenghua.yu@intel.com,
	Megha Dey <megha.dey@linux.intel.com>
Subject: [PATCH 2/6] crypto: sha512-mb - Enable SHA512 multibuffer support
Date: Mon, 27 Jun 2016 10:20:05 -0700	[thread overview]
Message-ID: <1467048009-2826-3-git-send-email-megha.dey@intel.com> (raw)
In-Reply-To: <1467048009-2826-1-git-send-email-megha.dey@intel.com>

From: Megha Dey <megha.dey@linux.intel.com>

Add the config CRYPTO_SHA512_MB which will enable the computation
using the SHA512 multi-buffer algorithm.

Signed-off-by: Megha Dey <megha.dey@linux.intel.com>
Reviewed-by: Fenghua Yu <fenghua.yu@intel.com>
Reviewed-by: Tim Chen <tim.c.chen@linux.intel.com>
---
 crypto/Kconfig | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/crypto/Kconfig b/crypto/Kconfig
index d8cc0f0..62fcbb9 100644
--- a/crypto/Kconfig
+++ b/crypto/Kconfig
@@ -720,6 +720,22 @@ config CRYPTO_SHA256_MB
 	  lanes remain unfilled, a flush operation will be initiated to
 	  process the crypto jobs, adding a slight latency.
 
+config CRYPTO_SHA512_MB
+        tristate "SHA512 digest algorithm (x86_64 Multi-Buffer, Experimental)"
+        depends on X86 && 64BIT
+        select CRYPTO_SHA512
+        select CRYPTO_HASH
+        select CRYPTO_MCRYPTD
+        help
+          SHA-512 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
+          using multi-buffer technique.  This algorithm computes on
+          multiple data lanes concurrently with SIMD instructions for
+          better throughput.  It should not be enabled by default but
+          used when there is significant amount of work to keep the keep
+          the data lanes filled to get performance benefit.  If the data
+          lanes remain unfilled, a flush operation will be initiated to
+          process the crypto jobs, adding a slight latency.
+
 config CRYPTO_SHA256
 	tristate "SHA224 and SHA256 digest algorithm"
 	select CRYPTO_HASH
-- 
1.9.1

  parent reply	other threads:[~2016-06-27 17:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-27 17:20 [PATCH 0/6] crypto: SHA512 multibuffer implementation Megha Dey
2016-06-27 17:20 ` [PATCH 1/6] crypto: sha512-mb - SHA512 multibuffer job manager and glue code Megha Dey
2016-06-27 17:20 ` Megha Dey [this message]
2016-06-27 17:20 ` [PATCH 3/6] crypto: sha512-mb - submit/flush routines for AVX2 Megha Dey
2016-06-27 17:20 ` [PATCH 4/6] crypto: sha512-mb - Algorithm data structures Megha Dey
2016-06-27 17:20 ` [PATCH 5/6] crypto: sha512-mb - Crypto computation (x4 AVX2) Megha Dey
2016-06-27 17:20 ` [PATCH 6/6] crypto: tcrypt - Add new mode for sha512_mb Megha Dey
2016-06-28  8:37 ` [PATCH 0/6] crypto: SHA512 multibuffer implementation Herbert Xu
  -- strict thread matches above, loose matches on Subject: below --
2016-03-24 20:27 megha.dey
2016-03-24 20:27 ` [PATCH 2/6] crypto: sha512-mb - Enable SHA512 multibuffer support megha.dey

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=1467048009-2826-3-git-send-email-megha.dey@intel.com \
    --to=megha.dey@intel.com \
    --cc=davem@davemloft.net \
    --cc=fenghua.yu@intel.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=megha.dey@linux.intel.com \
    --cc=tim.c.chen@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