Received-SPF: pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Stephan Mueller <smueller@chronox.de>
To:     Nikolay Borisov <nborisov@suse.com>
Cc:     Eric Biggers <ebiggers@kernel.org>, herbert@gondor.apana.org.au,
        davem@davemloft.net, linux-crypto@vger.kernel.org, terrelln@fb.com,
        jthumshirn@suse.de
Subject: Re: [PATCH] crypto: xxhash - Implement xxhash support
Date:   Tue, 28 May 2019 07:59:17 +0200
Message-ID: <2084703.uDJgg2HtUG@tauon.chronox.de>
In-Reply-To: <b9311cb4-3d59-1e97-4967-2f430c4918ad@suse.com>
References: <20190527142810.31472-1-nborisov@suse.com> <1778879.ZR4uXBBfnJ@tauon.chronox.de> <b9311cb4-3d59-1e97-4967-2f430c4918ad@suse.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"
Sender: linux-crypto-owner@vger.kernel.org
Precedence: bulk

Am Dienstag, 28. Mai 2019, 07:58:19 CEST schrieb Nikolay Borisov:

Hi Nikolay,

> On 28.05.19 =D0=B3. 7:58 =D1=87., Stephan Mueller wrote:
> > Please correct me if I am wrong, but as far as I see, however, xxhash
> > seems to be a cryptographic hash function.
>=20
> No, xxhash is non-cryptographic. THe official description from
> xxhash.com states:
>=20
> xxHash is an extremely fast non-cryptographic hash algorithm, working at
> speeds close to RAM limits. It is proposed in two flavors, 32 and 64 bits.

I see, then please disregard my comment on the FIPS flag then.

Ciao
Stephan