Messages in this thread | | | Subject | Re: [PATCH 3/4] crypto: [sha] glue code for Intel SHA extensions optimized SHA1 & SHA256 | From | Tim Chen <> | Date | Fri, 11 Sep 2015 13:10:27 -0700 |
| |
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
| |