Linux cryptographic layer development
 help / color / mirror / Atom feed
From: megha.dey@linux.intel.com
To: herbert@gondor.apana.org.au, davem@davemloft.net
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	tim.c.chen@linux.intel.com, fenghua.yu@intel.com,
	Megha Dey <megha.dey@intel.com>,
	Megha Dey <megha.dey@linux.intel.com>
Subject: [PATCH 3/7] crypto: sha256-mb - Enable multibuffer support
Date: Thu, 24 Mar 2016 13:25:59 -0700	[thread overview]
Message-ID: <1458851163-3448-4-git-send-email-megha.dey@linux.intel.com> (raw)
In-Reply-To: <1458851163-3448-1-git-send-email-megha.dey@linux.intel.com>

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

Add the config CRYPTO_SHA256_MB which will enable the computation using the
SHA256 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 f6bfdda..3c763d8 100644
--- a/crypto/Kconfig
+++ b/crypto/Kconfig
@@ -678,6 +678,22 @@ config CRYPTO_SHA1_MB
 	  lanes remain unfilled, a flush operation will be initiated to
 	  process the crypto jobs, adding a slight latency.
 
+config CRYPTO_SHA256_MB
+	tristate "SHA256 digest algorithm (x86_64 Multi-Buffer, Experimental)"
+	depends on X86 && 64BIT
+	select CRYPTO_SHA256
+	select CRYPTO_HASH
+	select CRYPTO_MCRYPTD
+	help
+	  SHA-256 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-03-24 20:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24 20:25 [PATCH 0/7] crypto: SHA256 multibuffer implementation megha.dey
2016-03-24 20:25 ` [PATCH 1/7] crypto: sha1-mb - rename sha-mb to sha1-mb megha.dey
2016-03-24 20:25 ` [PATCH 2/7] crypto: sha256-mb - SHA256 multibuffer job manager and glue code megha.dey
2016-04-05 12:03   ` Herbert Xu
2016-04-08 18:37     ` Yu, Fenghua
2016-03-24 20:25 ` megha.dey [this message]
2016-03-24 20:26 ` [PATCH 4/7] crypto: sha256-mb - submit/flush routines for AVX2 megha.dey
2016-04-11  6:13   ` Xiaodong Liu
2016-03-24 20:26 ` [PATCH 5/7] crypto: sha256-mb - Algorithm data structures megha.dey
2016-03-24 20:26 ` [PATCH 6/7] crypto: sha256-mb - Crypto computation (x8 AVX2) megha.dey
2016-03-24 20:26 ` [PATCH 7/7] crypto: tcrypt - Add speed tests for SHA multibuffer algorithms megha.dey
2016-04-04 23:06 ` [PATCH 0/7] crypto: SHA256 multibuffer implementation Yu, Fenghua

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=1458851163-3448-4-git-send-email-megha.dey@linux.intel.com \
    --to=megha.dey@linux.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@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