From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: dm-crypt@saout.de
Subject: [dm-crypt] dm-crypt multithreaded yet?
Date: Wed, 08 Aug 2012 10:29:01 -0400 [thread overview]
Message-ID: <jvtt3d$1lm$1@dough.gmane.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]
Hi all.
Sorry for what is probably a very tiresome topic here, but just trying
to find out what the current status is...
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.
Is this something being worked on currently?
I have taken note of
http://people.redhat.com/mpatocka/patches/kernel/dm-crypt-paralelizace/current/
but that work seems to be going back to Feb/2012. And TBH, I'm not
entirely clear if that work is aimed at multi-threaded dm-crypt or not.
Cheers,
b.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next reply other threads:[~2012-08-08 14:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 14:29 Brian J. Murrell [this message]
2012-08-08 15:31 ` [dm-crypt] dm-crypt multithreaded yet? 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
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='jvtt3d$1lm$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 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.