From: Matthias Schniedermeyer <ms@citd.de>
To: "Brian J. Murrell" <brian@interlinx.bc.ca>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Using AES-256 Controller Card
Date: Mon, 27 Aug 2012 20:56:49 +0200 [thread overview]
Message-ID: <20120827185649.GA12656@citd.de> (raw)
In-Reply-To: <k1gelu$ul9$1@ger.gmane.org>
On 27.08.2012 14:35, Brian J. Murrell wrote:
> On 12-08-27 02:16 PM, Matthias Schniedermeyer wrote:
> >
> > Contrary to OP: AES-NI
>
> OP doesn't have AES-NI so it's performance gains are orthogonal.
>
> > So it's between 1066.52 MiB/s and 1027.7 MiB/s
>
> Sure, but OP doesn't have AES-NI on his CPU, so I'm not sure the point.
Hmm. I reread the original post and i have to say: It's ambiguous.
What i read, and what stuck in my head, was "dmcrypt doesn't support
AES-NI", not "my CPU doesn't support AES-NI".
But i guess the OP meant the latter, so my mistake.
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
prev parent reply other threads:[~2012-08-27 18:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-26 18:00 [dm-crypt] Using AES-256 Controller Card Michael Wisniewski
2012-08-27 13:42 ` Michael Wisniewski
2012-08-27 15:23 ` Milan Broz
2012-08-27 15:24 ` Michael Wisniewski
2012-08-27 15:33 ` Brian J. Murrell
2012-08-27 18:16 ` Matthias Schniedermeyer
2012-08-27 18:31 ` Michael Wisniewski
2012-08-27 18:35 ` Brian J. Murrell
2012-08-27 18:56 ` Matthias Schniedermeyer [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=20120827185649.GA12656@citd.de \
--to=ms@citd.de \
--cc=brian@interlinx.bc.ca \
--cc=dm-crypt@saout.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.