> -----Original Message----- > From: linux-btrfs-ow...@vger.kernel.org <linux-btrfs- > ow...@vger.kernel.org> On Behalf Of Paul Jones > Sent: Friday, 23 August 2019 7:39 PM > To: Peter Becker <floyd....@gmail.com>; Holger Hoffstätte > <hol...@applied-asynchrony.com> > Cc: Linux BTRFS Mailinglist <linux-btrfs@vger.kernel.org> > Subject: RE: [PATCH v2 0/4] Support xxhash64 checksums > > > -----Original Message----- > > From: linux-btrfs-ow...@vger.kernel.org <linux-btrfs- > > ow...@vger.kernel.org> On Behalf Of Peter Becker > > Sent: Friday, 23 August 2019 1:40 AM > > To: Holger Hoffstätte <hol...@applied-asynchrony.com> > > Cc: Linux BTRFS Mailinglist <linux-btrfs@vger.kernel.org> > > Subject: Re: [PATCH v2 0/4] Support xxhash64 checksums > > > > Am Do., 22. Aug. 2019 um 16:41 Uhr schrieb Holger Hoffstätte > > <hol...@applied-asynchrony.com>: > > > but how does btrfs benefit from this compared to using crc32-intel? > > > > As i know, crc32c is as far as ~3x faster than xxhash. But xxHash was > > created with a differend design goal. > > If you using a cpu without hardware crc32 support, xxHash provides you > > a maximum portability and speed. Look at arm, mips, power, etc. or old > > intel cpus like Core 2 Duo. > > I've got a modified version of smhasher > (https://github.com/PeeJay/smhasher) that tests speed and cryptographics > of various hashing functions.
I forgot to add xxhash32 Crc32 Software - 379.91 MiB/sec Crc32 Hardware - 7338.60 MiB/sec XXhash64 Software - 12094.40 MiB/sec XXhash32 Software - 6060.11 MiB/sec Testing done on a 1st Gen Ryzen. Impressive numbers from XXhash64. Paul.
