Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755863AbYHDRGY (ORCPT ); Mon, 4 Aug 2008 13:06:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752190AbYHDRGQ (ORCPT ); Mon, 4 Aug 2008 13:06:16 -0400 Received: from casper.infradead.org ([85.118.1.10]:32867 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753715AbYHDRGP (ORCPT ); Mon, 4 Aug 2008 13:06:15 -0400 Date: Mon, 4 Aug 2008 10:06:05 -0700 From: Arjan van de Ven To: Herbert Xu Cc: chris.mason@oracle.com (Chris Mason), herbert@gondor.apana.org.au, dwmw2@infradead.org, austin_zhang@linux.intel.com, davem@davemloft.net, linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org Subject: Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API. Message-ID: <20080804100605.4f0921f4@infradead.org> In-Reply-To: References: <1217866496.29139.75.camel@think.oraclecorp.com> Organization: Intel X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.11; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SRS-Rewrite: SMTP reverse-path rewritten from by casper.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 763 Lines: 21 On Tue, 05 Aug 2008 00:45:34 +0800 Herbert Xu wrote: > On the other hand, one of the advantages of doing it through the > crypto API is that this kind of selection is useful for quite a > few operations, e.g., xor or even memcpy. well you still have that indirect function call for libcrc32 we could alternatives() that... -- If you want to reach me at my work email, use arjan@linux.intel.com For development, discussion and tips for power savings, visit http://www.lesswatts.org -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/