From: David Miller <davem@davemloft.net>
To: tim.c.chen@linux.intel.com
Cc: herbert@gondor.apana.org.au, hpa@zytor.com,
sean.m.gulley@intel.com, mouli_7982@yahoo.com,
vinodh.gopal@intel.com, james.guilford@intel.com,
wajdi.k.feghali@intel.com, jussi.kivilinna@iki.fi,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] crypto: [sha] x86 SHA extension optimization of SHA1 and SHA256
Date: Thu, 10 Sep 2015 15:56:06 -0700 (PDT) [thread overview]
Message-ID: <20150910.155606.944423642222505007.davem@davemloft.net> (raw)
In-Reply-To: <1441924012.4322.0.camel@schen9-desk2.jf.intel.com>
From: Tim Chen <tim.c.chen@linux.intel.com>
Date: Thu, 10 Sep 2015 15:26:52 -0700
>
> The new x86 SHA extensions provide new hardware accelerated instructions
> for computing SHA1 and SHA256 hashes. This patch series provide the
> assembly routines for SHA1 and SHA256 computation using these new
> instructions to the kernel crypto library. For 4K data blocks, we've
> seen up to 3.6x speedup over existing SSSE3 enhanced routines in the
> kernel crypto library on Broxton platform.
>
> Refer to SHA extension programming guide in chapter 8.2 of the
> Intel Architecture Instruction Set Extensions Programming reference.
> https://software.intel.com/sites/default/files/managed/07/b7/319433-023.pdf
>
> Pre-req patches:
> [1] [PATCH] sha: Enable cpuid check for Intel SHA extensions implementations
> http://marc.info/?l=linux-kernel&m=144019424304089&w=2
> [2] [Patch] x86/insn: perf tools: Add new SHA instructions
> http://marc.info/?l=linux-kernel&m=144119645000679&w=2
Series looks fine to me:
Acked-by: David S. Miller <davem@davemloft.net>
next prev parent reply other threads:[~2015-09-10 22:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 22:26 Tim Chen
2015-09-10 22:56 ` David Miller [this message]
2015-09-18 14:03 ` 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=20150910.155606.944423642222505007.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=hpa@zytor.com \
--cc=james.guilford@intel.com \
--cc=jussi.kivilinna@iki.fi \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mouli_7982@yahoo.com \
--cc=sean.m.gulley@intel.com \
--cc=tim.c.chen@linux.intel.com \
--cc=vinodh.gopal@intel.com \
--cc=wajdi.k.feghali@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
all inboxes | Powered by JetHome®