From: Jussi Kivilinna Subject: Re: [PATCH] crypto: fix FTBFS with ARM SHA1-asm and THUMB2_KERNEL Date: Tue, 22 Jan 2013 09:50:21 +0200 Message-ID: <20130122095021.89432qdbeu32a4sg@www.dalek.fi> References: <1358787763-1226-1-git-send-email-matt@genesi-usa.com> <20130122094614.79031aq5ddrgr2zo@www.dalek.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Transfer-Encoding: 7bit Cc: Matt Sealey , Nicolas Pitre , LKML , linux-crypto@vger.kernel.org, "David S. Miller" , Herbert Xu , Russell King , Linux ARM Kernel ML , Dave Martin , David McCullough To: Jussi Kivilinna Return-path: Received: from sd-mail-sa-02.sanoma.fi ([158.127.18.162]:35530 "EHLO sd-mail-sa-02.sanoma.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754347Ab3AVHuY (ORCPT ); Tue, 22 Jan 2013 02:50:24 -0500 In-Reply-To: <20130122094614.79031aq5ddrgr2zo@www.dalek.fi> Content-Disposition: inline Sender: linux-crypto-owner@vger.kernel.org List-ID: Quoting Jussi Kivilinna : > Quoting Matt Sealey : > >> This question is to the implementor/committer (Dave McCullough), how >> exactly did you measure the benchmark and can we reproduce it on some >> other ARM box? >> >> If it's long and laborious and not so important to test the IPsec >> tunnel use-case, what would be the simplest possible benchmark to see >> if the C vs. assembly version is faster for a particular ARM device? I >> can get hold of pretty much any Cortex-A8 or Cortex-A9 that matters, I >> have access to a Chromebook for A15, and maybe an i.MX27 or i.MX35 and >> a couple Marvell boards (ARMv6) if I set my mind to it... that much >> testing implies we find a pretty concise benchmark though with a >> fairly common kernel version we can spread around (i.MX, OMAP and the >> Chromebook, I can handle, the rest I'm a little wary of bothering to >> spend too much time on). I think that could cover a good swath of >> not-ARMv5 use cases from lower speeds to quad core monsters.. but I >> might stick to i.MX to start with.. > > There is 'tcrypt' module in crypto/ for quick benchmarking. > 'modprobe tcrypt mode=500 sec=1' tests AES in various cipher-modes, > using different buffer sizes and outputs results to kernel log. > Actually mode=200 might be better, as mode=500 is for asynchronous implementations and might use hardware crypto if such device/module is available. -Jussi