From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qg0-f51.google.com ([209.85.192.51]:54051 "EHLO mail-qg0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932731AbaLBAaL (ORCPT ); Mon, 1 Dec 2014 19:30:11 -0500 Received: by mail-qg0-f51.google.com with SMTP id l89so8567767qgf.10 for ; Mon, 01 Dec 2014 16:30:10 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <1416806586-18050-1-git-send-email-bo.li.liu@oracle.com> <20141125163905.GJ26471@twin.jikos.cz> <547C618C.8020201@gmail.com> <547CA870.9040904@gmail.com> Date: Mon, 1 Dec 2014 16:30:09 -0800 Message-ID: Subject: Re: [RFC PATCH] Btrfs: add sha256 checksum option From: John Williams To: Alex Elsayed Cc: Btrfs BTRFS Content-Type: text/plain; charset=UTF-8 Sender: linux-btrfs-owner@vger.kernel.org List-ID: On Mon, Dec 1, 2014 at 4:15 PM, Alex Elsayed wrote: > There's a thing called the transitive property. When CRC32 is faster than > SpookyHash and CityHash (while admittedly weaker), and SHA-1 on SPARC is > faster than CRC32, there are comparisons that can be made. And yet you applied the transitive property with poor assumptions and in a convoluted way to come up with an incorrect conclusion. > It's that the flat assertion that "CityHash/SpookyHash/etc is always faster" > is _unwarranted_, as hardware acceleration _has a huge effect_. Actually, the assertion is true and backed up by evidence that I cited. I'm not sure why you think hardware acceleration only helps SHA-1 and does not help CityHash or SpookyHash.