From: matt@genesi-usa.com (Matt Sealey)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] crypto: fix FTBFS with ARM SHA1-asm and THUMB2_KERNEL
Date: Tue, 22 Jan 2013 13:43:54 -0600 [thread overview]
Message-ID: <CAKGA1bmJwb94h0SVNW7WZkSYAPWeAUpm86D+SsvnOJ5NSNbe_g@mail.gmail.com> (raw)
In-Reply-To: <20130122095021.89432qdbeu32a4sg@www.dalek.fi>
On Tue, Jan 22, 2013 at 1:50 AM, Jussi Kivilinna
<jussi.kivilinna@mbnet.fi> wrote:
>
>> 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.
Okeydokey I'll start running some tests..
--
Matt Sealey <matt@genesi-usa.com>
Product Development Analyst, Genesi USA, Inc.
prev parent reply other threads:[~2013-01-22 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 17:02 [PATCH] crypto: fix FTBFS with ARM SHA1-asm and THUMB2_KERNEL Matt Sealey
2013-01-21 22:46 ` Nicolas Pitre
2013-01-22 0:54 ` Matt Sealey
2013-01-22 7:46 ` Jussi Kivilinna
2013-01-22 7:50 ` Jussi Kivilinna
2013-01-22 19:43 ` Matt Sealey [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKGA1bmJwb94h0SVNW7WZkSYAPWeAUpm86D+SsvnOJ5NSNbe_g@mail.gmail.com \
--to=matt@genesi-usa.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).