DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jakob Sandgren <jakob@southpole.se>
To: dm-crypt@saout.de
Subject: [dm-crypt] Poor performane (idle cpu)
Date: Mon, 8 Feb 2010 02:16:54 +0100	[thread overview]
Message-ID: <20100208011654.GA4927@southpole.se> (raw)

Hi,

I'm using dm-crypt for several mappings with a hardware raid backend. 
Using a raw read from the raid device (e.g sda) gives ~250MB/s

But when I read from an encrypted mapping, I just get ~70MB/s. That
should be fine if I at least have the kcryptd process using a core at
100%, but that is not the case. Three of my four cores is 99% idle and
one core is 50% idle (aprox.).

I have recently upgraded my hardware from an older quadcore system
(AMD) to a new Core I7 (860) and expected improved performance and
when I did not get that, then did I do some more investegation and
found out above. I have also read posts from others having the same
problems, but no explanation.

Anyone who has an explanation for this or a hint if one could
"tune" anything to get better performance? 

Output from "cryptsetup status":

/dev/mapper//dev/mapper/shared1 is active:
  cipher:  aes-cbc-essiv:sha256
  keysize: 128 bits
  device:  /dev/mapper/areca_0_1-shared1_raw
  offset:  1032 sectors
  size:    3145726968 sectors
  mode:    read/write


Best Regards,
Jakob


-- 

             reply	other threads:[~2010-02-08  1:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-08  1:16 Jakob Sandgren [this message]
2010-02-08  1:50 ` [dm-crypt] Poor performane (idle cpu) Arno Wagner
2010-02-08 23:54 ` Jakob Sandgren
2010-02-09  0:28   ` Arno Wagner
2010-02-09 14:48     ` [dm-crypt] Poor performane (idle cpu) [SOLVED; problem with "pv"] Jakob Sandgren
2010-02-09 16:14       ` Arno Wagner
2010-02-09 16:16       ` M Thomas Frederiksen

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=20100208011654.GA4927@southpole.se \
    --to=jakob@southpole.se \
    --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