DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Krainz <ldm@gmx.at>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Improving performance?
Date: Thu, 11 Nov 2010 19:56:30 +0100	[thread overview]
Message-ID: <4CDC3C5E.1020108@gmx.at> (raw)

[-- Attachment #1: Type: text/plain, Size: 1903 bytes --]


On 2010-11-11 19:26, Lasse Jensen wrote:
> I havent tested my current setup this way, but my old setup, RAID 
> first, then encryption worked fine.

RAID first, den ecryption works for me, too.
But testing the ecrypting drives seperately, then RAID approach failed.
What good is fast performance if the RAID 5 does not work? :D

>     dmcrypt/luks is used on top of the raid. The performance of the i5
>     is not great, despite hardware aes. Should not be this numbers a
>     bit higher than 158 MB/sec?
>
>     ~/httptunnel-3.3/ hdparm -t --direct /dev/md1
>
>     /dev/md1:
>      Timing O_DIRECT disk reads:  936 MB in  3.00 seconds = 311.67 MB/sec
>
>     ~/httptunnel-3.3/ hdparm -t --direct /dev/mapper/evol
>
>     /dev/mapper/evol:
>      Timing O_DIRECT disk reads:  476 MB in  3.01 seconds = 158.30 MB/sec
>
>     cat /proc/cpuinfo | grep -E (model name|aes)
>     model name      : Intel(R) Core(TM) i5 CPU         660  @ 3.33GHz
>     flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr
>     pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
>     pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts
>     rep_good xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64
>     monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2
>     popcnt aes lahf_lm ida arat dts tpr_shadow vnmi flexpriority ept vpid
>
>
> Well, it's still a lot better than my setup. Have you got any idea how 
> much power your system uses idle and under load?
>

I am afraid I cannot unplug the server right now and I do not have an 
ampere meter lying around.
But I went for a 32nm dual-core-CPU, a small motherboard with lots of 
sata plugs and an efficient power supply, so I figured you can not get 
much better power
consumption wise.

Forgot to mention, the above hdparam -t result is for cipher mode: 
xts-plain64 and AES-256.

Regards,

Markus Krainz


[-- Attachment #2: Type: text/html, Size: 3663 bytes --]

             reply	other threads:[~2010-11-11 18:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-11 18:56 Markus Krainz [this message]
2010-11-12  1:21 ` [dm-crypt] Improving performance? Arno Wagner
2010-11-12  5:00   ` dave b
2010-11-12  7:10     ` Heinz Diehl
  -- strict thread matches above, loose matches on Subject: below --
2010-11-11 10:49 Lasse Jensen
2010-11-11 11:30 ` Arno Wagner
2010-11-11 18:16   ` Lasse Jensen
2010-11-11 17:03 ` Heinz Diehl
2010-11-11 17:06   ` Rick Moritz
2010-11-11 20:59     ` Heinz Diehl
2010-11-11 21:25       ` Rick Moritz
2010-11-11 18:19   ` Lasse Jensen
2010-11-11 17:40 ` Zdenek Kaspar
2010-11-11 17:59 ` Markus Krainz
2010-11-11 19:10   ` epvdm
2010-11-11 21:24 ` Richard Zidlicky

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=4CDC3C5E.1020108@gmx.at \
    --to=ldm@gmx.at \
    --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