From: mfuzzey@parkeon.com (Martin Fuzzey)
To: linux-arm-kernel@lists.infradead.org
Subject: Sahara performance on i.MX53
Date: Mon, 27 Apr 2015 19:16:22 +0200 [thread overview]
Message-ID: <553E6EE6.2050803@parkeon.com> (raw)
Hi,
I've been trying the Sahara crypto module on i.MX53 [mainline 3.19
kernel + b251638c46a (crypto: sahara - use the backlog)]
I tested using dm-crypt with AES-128:
cryptsetup -v --key-size=128 luksFormat /dev/mmcblk0p7
cryptsetup luksOpen /dev/mmcblk0p7 cryptotest
dd if=/dev/mapper/cryptotest of=/dev/null bs=1M count=100
CPU Freq (MHz) Time (s) WITHOUT Sahara Time (s) WITH Sahara
1200 3.26 5.34
1000 3.26 5.62
800 4.0 6.24
400 7.72 9.86
166 18.42 18.87
I was hoping for something better.
There is a reduction in CPU usage as expected but the performance
figures aren't looking very good.
As this is in kernel use by dm-crypt cryptodev or af_alg aren't involved.
Has anyone else done any measurements?
Something wrong with my setup or with my expectations?
Regards,
Martin
next reply other threads:[~2015-04-27 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 17:16 Martin Fuzzey [this message]
2015-04-27 17:34 ` Sahara performance on i.MX53 Steffen Trumtrar
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=553E6EE6.2050803@parkeon.com \
--to=mfuzzey@parkeon.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).