From: Herbert Xu Subject: Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API. Date: Tue, 5 Aug 2008 01:13:16 +0800 Message-ID: <20080804171316.GA13819@gondor.apana.org.au> References: <1217866496.29139.75.camel@think.oraclecorp.com> <20080804100605.4f0921f4@infradead.org> <20080804171017.GA13725@gondor.apana.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Chris Mason , dwmw2@infradead.org, austin_zhang@linux.intel.com, davem@davemloft.net, linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org To: Arjan van de Ven Return-path: Received: from rhun.apana.org.au ([64.62.148.172]:36692 "EHLO arnor.apana.org.au" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753646AbYHDRNf (ORCPT ); Mon, 4 Aug 2008 13:13:35 -0400 Content-Disposition: inline In-Reply-To: <20080804171017.GA13725@gondor.apana.org.au> Sender: linux-crypto-owner@vger.kernel.org List-ID: On Tue, Aug 05, 2008 at 01:10:17AM +0800, Herbert Xu wrote: > > I don't see why you couldn't do that for the crypto API too > if you wanted to. That way it would benefit all crypto users > rather than just the crc32c (note the extra c) users. Anyway, the point here is the crc32c is nothing special. It's just one out of many algorithms that has/will have hardware acceleration support. Rather than doing ad-hoc implementations and optimising that whenever such a thing pops up, let's spend our effort in creating a common platform that can be reused. 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