From: john terragon <terragonjohn@yahoo.com>
To: Milan Broz <mbroz@redhat.com>
Cc: linux-crypto@vger.kernel.org
Subject: Re: aesni-intel slower than aes-x86_64
Date: Mon, 12 Apr 2010 10:09:36 -0700 (PDT) [thread overview]
Message-ID: <263254.5283.qm@web45116.mail.sp1.yahoo.com> (raw)
In-Reply-To: <4BC3150A.1080905@redhat.com>
--- On Mon, 4/12/10, Milan Broz <mbroz@redhat.com> wrote:
> From: Milan Broz <mbroz@redhat.com>
> Subject: Re: aesni-intel slower than aes-x86_64
> To: "john terragon" <terragonjohn@yahoo.com>
> Cc: linux-crypto@vger.kernel.org
> Date: Monday, April 12, 2010, 5:41 AM
> 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.
>
With iflag=direct I get about 1.2 MB/sec more or less in all the three cases. With bs=1M I get slightly better results in all the three cases
however the increase for aesni is proportionally less than the other two cases. So the performance differences are even slightly larger with bs=1M. I don't get it. As it is, it seems that the aes new instructions are practically useless (with my core i5 520M, at least).
John
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-04-12 17:09 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
2010-04-12 17:09 ` john terragon [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=263254.5283.qm@web45116.mail.sp1.yahoo.com \
--to=terragonjohn@yahoo.com \
--cc=linux-crypto@vger.kernel.org \
--cc=mbroz@redhat.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