From: Milan Broz <mbroz@redhat.com>
To: john terragon <terragonjohn@yahoo.com>
Cc: linux-crypto@vger.kernel.org
Subject: Re: aesni-intel slower than aes-x86_64
Date: Mon, 12 Apr 2010 14:41:46 +0200 [thread overview]
Message-ID: <4BC3150A.1080905@redhat.com> (raw)
In-Reply-To: <693236.82640.qm@web45101.mail.sp1.yahoo.com>
On 04/12/2010 12:52 AM, john terragon wrote:
> My system has a core i5 520M and supports AES-NI. I wanted to do a
> rude performance test and so I ran these commands on a small (4GB) partition and on the dm-crypt device backed by it:
>
> 1) using the aesni-intel module: dd if=/dev/dev/mapper/vol of=/dev/null bs=4k
> 2) using only the generic aes-x86_64 module: dd if=/dev/dev/mapper/vol
> of=/dev/null bs=4k
> 3) dd if=/dev/sda4 of=/dev/null bs=4k
>
> What I got kind of surprised me:
> 1) ~ 67 MB/sec, with a low cpu load by kcryptd
> 2) ~ 79 MB/sec, with a higher cpu load by kcryptd
> 3) ~ 81 MB/sec
Just curious - is it the same if you add iflag=direct? Also try larger block size bs=1M etc.
Milan
next prev parent reply other threads:[~2010-04-12 12:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-11 22:52 aesni-intel slower than aes-x86_64 john terragon
2010-04-12 12:41 ` Milan Broz [this message]
2010-04-12 17:09 ` john terragon
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=4BC3150A.1080905@redhat.com \
--to=mbroz@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=terragonjohn@yahoo.com \
/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