From: Tim Chen <tim.c.chen@linux.intel.com>
To: David Miller <davem@davemloft.net>
Cc: smueller@chronox.de, 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 3/4] crypto: [sha] glue code for Intel SHA extensions optimized SHA1 & SHA256
Date: Fri, 11 Sep 2015 13:10:27 -0700 [thread overview]
Message-ID: <1442002227.4322.45.camel@schen9-desk2.jf.intel.com> (raw)
In-Reply-To: <20150911.121509.844598934515668336.davem@davemloft.net>
On Fri, 2015-09-11 at 12:15 -0700, David Miller wrote:
> From: Tim Chen <tim.c.chen@linux.intel.com>
> Date: Fri, 11 Sep 2015 11:49:32 -0700
>
> > Still, why would some kernel module specifically not want to
> > use the fastest HW implementation, and explicitly ask for
> > a slower driver?
>
> Temporary workaround if a bug is found.
>
> There is really no reason to prevent the user from having this
> flexibility, and in return anyone can test any implementation
> their cpu can support.
Mmmm..., this is a restructuring of the algorithms within
the glue code into multiple drivers instead of one and exposing
them all. It is a bit orthogonal to the intention of this
patch set. I think it is better that I create a
separate patch on the glue code on top of this patch set
to implement this.
Herbert, do you agree with this approach?
Tim
next prev parent reply other threads:[~2015-09-11 20:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1441929717.git.tim.c.chen@linux.intel.com>
2015-09-10 22:26 ` [PATCH 1/4] crypto: [sha] Intel SHA Extensions optimized SHA1 transform function Tim Chen
2015-09-10 22:27 ` [PATCH 2/4] crypto: [sha] Intel SHA Extensions optimized SHA256 " Tim Chen
2015-09-10 22:27 ` [PATCH 3/4] crypto: [sha] glue code for Intel SHA extensions optimized SHA1 & SHA256 Tim Chen
2015-09-10 22:52 ` Stephan Mueller
2015-09-11 0:04 ` Tim Chen
2015-09-11 17:02 ` Stephan Mueller
2015-09-11 18:49 ` Tim Chen
2015-09-11 19:15 ` David Miller
2015-09-11 20:10 ` Tim Chen [this message]
2015-09-12 8:09 ` Herbert Xu
2015-09-11 19:15 ` Stephan Mueller
2015-09-10 22:27 ` [PATCH 4/4] crypto: [sha] Add build support for Intel SHA Extensions optimized SHA1 and SHA256 Tim Chen
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=1442002227.4322.45.camel@schen9-desk2.jf.intel.com \
--to=tim.c.chen@linux.intel.com \
--cc=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=smueller@chronox.de \
--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