From: Sam Bingner <sam@bingner.com>
To: Brad Campbell <lists2009@fnarfbargle.com>,
Christoph Anton Mitterer <calestyo@scientia.net>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: some general questions on RAID
Date: Fri, 5 Jul 2013 01:39:30 +0000 [thread overview]
Message-ID: <CDFB4726.1374F%sam@bingner.com> (raw)
In-Reply-To: <51D61DA5.9090507@fnarfbargle.com>
On 7/4/13 3:13 PM, "Brad Campbell" <lists2009@fnarfbargle.com> wrote:
>On 05/07/13 02:30, Christoph Anton Mitterer wrote:
>> Hi.
>>
>> Well for me personally these are follow up questions to my scenario
>> presented here: http://thread.gmane.org/gmane.linux.raid/43405
>>
>> But I think these questions would be generally interesting an I'd like
>> to add them to the Debian FAQ for mdadm (and haven't found real good
>> answers in the archives/google).
>>
>>
>> 1) I plan to use dmcrypt and LUKS and had the following stacking in
>> mind:
>> physical devices -> MD -> dmcrypt -> LVM (with multiple LVs) ->
>> filesystems
>
>I have two arrays with dmcrypt on top of MD.
>Array 1 is 4 x Seagate 15k SAS drives in a RAID10 f2.
>Array 2 is 6 x 240G SSD's in a RAID10 n2.
>
>Array 2 is partitoned. All run ext4.
>The CPU is an AMD FX8350. I can max out all arrays with sequential or
>random r/w loads. So dmcrypt is not a limiting factor for me.
>
>When I say max out, I run into bandwidth limits on the hardware before
>dmcrypt gets in the way.
>
That is because your CPU has encryption features - the QNAP devices
largely do not; I replaced the CPU in mine with one that had encryption
features because otherwise there was nothing that could bring the
performance above about 80MB/sec
Once I put in a CPU supporting AESNI I could get up to about 500MB/sec -
and this was still not CPU bound
next prev parent reply other threads:[~2013-07-05 1:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 18:30 some general questions on RAID Christoph Anton Mitterer
2013-07-04 22:07 ` Phil Turmel
2013-07-04 23:34 ` Christoph Anton Mitterer
2013-07-08 4:48 ` NeilBrown
2013-07-06 1:33 ` Christoph Anton Mitterer
2013-07-06 8:52 ` Stan Hoeppner
2013-07-06 15:15 ` Christoph Anton Mitterer
2013-07-07 16:51 ` Stan Hoeppner
2013-07-07 17:39 ` Milan Broz
2013-07-07 18:01 ` Christoph Anton Mitterer
2013-07-07 18:50 ` Milan Broz
2013-07-07 20:51 ` Christoph Anton Mitterer
2013-07-08 5:40 ` Milan Broz
2013-07-08 4:53 ` NeilBrown
2013-07-08 5:25 ` Milan Broz
2013-07-05 1:13 ` Brad Campbell
2013-07-05 1:39 ` Sam Bingner [this message]
2013-07-05 3:06 ` Brad Campbell
2013-07-06 1:23 ` some general questions on RAID (OT) Christoph Anton Mitterer
2013-07-06 6:23 ` Sam Bingner
2013-07-06 15:11 ` Christoph Anton Mitterer
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=CDFB4726.1374F%sam@bingner.com \
--to=sam@bingner.com \
--cc=calestyo@scientia.net \
--cc=linux-raid@vger.kernel.org \
--cc=lists2009@fnarfbargle.com \
/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.