From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752761AbbIKTPO (ORCPT ); Fri, 11 Sep 2015 15:15:14 -0400 Received: from shards.monkeyblade.net ([149.20.54.216]:49797 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751450AbbIKTPM (ORCPT ); Fri, 11 Sep 2015 15:15:12 -0400 Date: Fri, 11 Sep 2015 12:15:09 -0700 (PDT) Message-Id: <20150911.121509.844598934515668336.davem@davemloft.net> To: tim.c.chen@linux.intel.com 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 From: David Miller In-Reply-To: <1441997372.4322.37.camel@schen9-desk2.jf.intel.com> References: <1441929871.4322.15.camel@schen9-desk2.jf.intel.com> <1671234.vBOzL28The@tauon.atsec.com> <1441997372.4322.37.camel@schen9-desk2.jf.intel.com> X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Fri, 11 Sep 2015 12:15:12 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Tim Chen 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.