From: Herbert Xu Subject: Re: [PATCH 0/2] crypto: omap-sha1-md5: OMAP3 SHA1 & MD5 driver Date: Tue, 13 Apr 2010 22:48:43 +0800 Message-ID: <20100413144843.GD12695@gondor.apana.org.au> References: <1270744533.1666.9.camel@Nokia-N900> <20100413085921.GA8988@gondor.apana.org.au> <4BC43BEB.90901@nokia.com> <20100413100308.GA9600@gondor.apana.org.au> <4BC44446.2010405@nokia.com> <20100413121004.GB10822@gondor.apana.org.au> <4BC47543.1020508@nokia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Uri Simchoni , "linux-crypto@vger.kernel.org" To: Dmitry Kasatkin Return-path: Received: from ringil.hengli.com.au ([216.59.3.182]:52447 "EHLO arnor.apana.org.au" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751642Ab0DMOsx (ORCPT ); Tue, 13 Apr 2010 10:48:53 -0400 Content-Disposition: inline In-Reply-To: <4BC47543.1020508@nokia.com> Sender: linux-crypto-owner@vger.kernel.org List-ID: On Tue, Apr 13, 2010 at 04:44:35PM +0300, Dmitry Kasatkin wrote: > > Well it can... if reqa occupied hw all other requests will fallback to > sw sha1. That is unacceptable. If we had a user-space API that would mean a single request can tie up the hardware indefinitely. If your hardware is not able to produce a non-finalised hash, then you should only do finup/final in hardware, and use a software fallback to implement the rest. If your hardware is also not able to accept an initial state, then the only thing you can implement is digest. The rest would have to fall back to software. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt