From: Marc MERLIN <marc@merlins.org>
To: "Thomas Bächler" <thomas@archlinux.org>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] dm-crypt multithreaded yet?
Date: Wed, 8 Aug 2012 20:17:58 -0700 [thread overview]
Message-ID: <20120809031758.GB12014@merlins.org> (raw)
In-Reply-To: <5022864F.8030402@archlinux.org>
[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]
Am 08.08.2012 16:29, schrieb Brian J. Murrell:
> I thought I knew the answer to this question (dm-crypt multithreaded
> yet? no) but I had read in several places that dm-crypt had gained
> multithreaded capabilities. I'm still skeptical though. I certainly
> don't see it on Fedora 17's 3.3.4-5.fc17.x86_64 kernel.
>
> Sadly, I don't have an AES-NI capable CPU, but I do have 4 (real, 8 with
> HT enabled) cores and dm-crypting on my SSD reduces its performance down
> from about 260MB/s (native) to 95MB/s. :-( I would like to think I
> could get more performance out of it if more of the (usually available
> anyway) CPU could be thrown at it.
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
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 308 bytes --]
next prev parent reply other threads:[~2012-08-09 3:18 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 [this message]
2012-08-09 10:09 ` Brian J. Murrell
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=20120809031758.GB12014@merlins.org \
--to=marc@merlins.org \
--cc=dm-crypt@saout.de \
--cc=thomas@archlinux.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 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.