From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751765AbcKGTlf (ORCPT ); Mon, 7 Nov 2016 14:41:35 -0500 Received: from frisell.zx2c4.com ([192.95.5.64]:43939 "EHLO frisell.zx2c4.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751360AbcKGTld (ORCPT ); Mon, 7 Nov 2016 14:41:33 -0500 MIME-Version: 1.0 In-Reply-To: <20161107192505.GB34388@google.com> References: <20161103004934.GA30775@gondor.apana.org.au> <20161103.130852.1456848512897088071.davem@davemloft.net> <20161104173723.GB34176@google.com> <20161107182646.GA34388@google.com> <20161107192505.GB34388@google.com> From: "Jason A. Donenfeld" Date: Mon, 7 Nov 2016 20:41:26 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] poly1305: generic C can be faster on chips with slow unaligned access To: Eric Biggers Cc: David Miller , Herbert Xu , linux-crypto@vger.kernel.org, LKML , Martin Willi , WireGuard mailing list , =?UTF-8?Q?Ren=C3=A9_van_Dorst?= 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 Mon, Nov 7, 2016 at 8:25 PM, Eric Biggers wrote: > No it does *not* buffer all incoming blocks, which is why the source pointer can > fall out of alignment. Yes, I actually tested this. In fact this situation is > even hit, in both possible places, in the self-tests. Urgh! v3 coming right up...