From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756175AbdIGV0y (ORCPT ); Thu, 7 Sep 2017 17:26:54 -0400 Received: from mail-wr0-f173.google.com ([209.85.128.173]:33749 "EHLO mail-wr0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755851AbdIGV0v (ORCPT ); Thu, 7 Sep 2017 17:26:51 -0400 X-Google-Smtp-Source: ADKCNb69Z2Sr1zcxUvp8fi7KQ4Qw+TuQd8+wcX4AH9SrjjwfHPdnecYhD4mErckEoRjW/YwFcGYsiQ== Date: Thu, 7 Sep 2017 23:26:47 +0200 From: Ingo Molnar To: Eric Biggers Cc: Josh Poimboeuf , x86@kernel.org, linux-kernel@vger.kernel.org, Tim Chen , Mathias Krause , Chandramouli Narayanan , Jussi Kivilinna , Peter Zijlstra , Herbert Xu , "David S. Miller" , linux-crypto@vger.kernel.org, Eric Biggers , Andy Lutomirski , Jiri Slaby Subject: Re: [PATCH 00/12] x86/crypto: Fix RBP usage in several crypto .S files Message-ID: <20170907212646.q3y5wmhyaaqblg5m@gmail.com> References: <20170902000919.GA139193@gmail.com> <20170907071534.ztbxvyfoo7m7esmw@gmail.com> <20170907175800.GA92996@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170907175800.GA92996@gmail.com> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Eric Biggers wrote: > On Thu, Sep 07, 2017 at 09:15:34AM +0200, Ingo Molnar wrote: > > > > * Eric Biggers wrote: > > > > > Thanks for fixing these! I don't have time to review these in detail, but I ran > > > the crypto self-tests on the affected algorithms, and they all pass. I also > > > benchmarked them before and after; the only noticable performance difference was > > > that sha256-avx2 and sha512-avx2 became a few percent slower. I don't suppose > > > there is a way around that? Otherwise it's probably not a big deal. > > > > Which CPU model did you use for the test? > > > > Thanks, > > > > Ingo > > This was on Haswell, "Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz". Any chance to test this with the latest microarchitecture - any Skylake derivative Intel CPU you have access to? Thanks, Ingo