From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757582AbcKBWAP (ORCPT ); Wed, 2 Nov 2016 18:00:15 -0400 Received: from frisell.zx2c4.com ([192.95.5.64]:34403 "EHLO frisell.zx2c4.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755930AbcKBWAN (ORCPT ); Wed, 2 Nov 2016 18:00:13 -0400 MIME-Version: 1.0 In-Reply-To: <20161102212657.GA26887@gondor.apana.org.au> References: <20161102175810.18647-1-Jason@zx2c4.com> <20161102200959.GA23297@gondor.apana.org.au> <20161102210802.GA26741@gondor.apana.org.au> <20161102212657.GA26887@gondor.apana.org.au> From: "Jason A. Donenfeld" Date: Wed, 2 Nov 2016 23:00:00 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] poly1305: generic C can be faster on chips with slow unaligned access To: Herbert Xu Cc: "David S. Miller" , linux-crypto@vger.kernel.org, LKML , Martin Willi Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 2, 2016 at 10:26 PM, Herbert Xu wrote: > What I'm interested in is whether the new code is sufficiently > close in performance to the old code, particularonly on x86. > > I'd much rather only have a single set of code for all architectures. > After all, this is meant to be a generic implementation. Just tested. I get a 6% slowdown on my Skylake. No good. I think it's probably best to have the two paths in there, and not reduce it to one.