From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] dm-crypt multithreaded yet?
Date: Thu, 09 Aug 2012 06:09:29 -0400 [thread overview]
Message-ID: <k0028p$eon$1@dough.gmane.org> (raw)
In-Reply-To: <20120809031758.GB12014@merlins.org>
[-- Attachment #1: Type: text/plain, Size: 484 bytes --]
On 12-08-08 11:17 PM, Marc MERLIN wrote:
>
> If that helps, my 500MB/s SSD is giving me 270MB/s when reading an encrypted
> file (i.e. going through the block and the filesystem layer) on my laptop:
> Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz
That would be AES-NI giving you that throughput. Unfortunately not all
of us have AES-NI (and nor can we just throw away an entire laptop just
to get it) but do have lots of idle cores sitting around that could help
out.
b.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-08-09 10:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 14:29 [dm-crypt] dm-crypt multithreaded yet? Brian J. Murrell
2012-08-08 15:31 ` Thomas Bächler
2012-08-08 15:45 ` Milan Broz
2012-08-09 3:17 ` Marc MERLIN
2012-08-09 10:09 ` Brian J. Murrell [this message]
2012-08-08 15:39 ` Milan Broz
2012-12-16 12:10 ` Brian J. Murrell
2012-12-16 18:15 ` Milan Broz
2012-12-16 21:29 ` Heinz Diehl
2012-12-16 21:43 ` Brian J. Murrell
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='k0028p$eon$1@dough.gmane.org' \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox