From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qg0-f41.google.com ([209.85.192.41]:33260 "EHLO mail-qg0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932382AbaLBAQS (ORCPT ); Mon, 1 Dec 2014 19:16:18 -0500 Received: by mail-qg0-f41.google.com with SMTP id j5so8613336qga.28 for ; Mon, 01 Dec 2014 16:16:18 -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:16:18 -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:06 PM, Alex Elsayed wrote: > https://github.com/openssl/openssl/blob/master/crypto/sha/asm/sha1-armv8.pl > > # hardware-assisted software(*) > # Apple A7 2.31 4.13 (+14%) > # Cortex-A53 2.19 8.73 (+108%) > # Cortex-A57 2.35 7.88 (+74%) Note that those are showing 2 cycles per byte. > From the CityHash readme, on a Xeon X5550 (which is _considerably_ more > powerful than any of the above): > > On a single core of a 2.67GHz Intel Xeon X5550, CityHashCrc256 peaks at > about 5 to 5.5 bytes/cycle. 5 bytes per cycle is 0.2 cycles per byte. So your own citation shows that CityHash is 10 times faster.