diff options
| author | Guilhem Moulin <guilhem@fripost.org> | 2014-01-23 07:40:58 +0100 |
|---|---|---|
| committer | Guilhem Moulin <guilhem@fripost.org> | 2015-06-07 04:27:58 +0200 |
| commit | 16e2c85922848adb1c21a46a6cc23846ef94b951 (patch) | |
| tree | 740413af17c446acf4478ed7e176caa881bdcf9e /src/fripost-postinst-udeb/debian/compat | |
| parent | ba40cbca9650e1ddaa8357c21b5de31cc376c481 (diff) | |
Enable RAID root system.
Quoting /usr/share/doc/cryptsetup/README.keyctl :
The current state for dm-crypt in Linux is that it is single threaded, thus
every dm-crypt mapping only uses a single core for crypto operations. To
use the full power of your many-core processor it is thus necessary to
split the dm-crypt device. For Linux software raid arrays the easiest
segmentation is to just put the dm-crypt layer below the software raid
layer.
However, this seems no longer true since 2.6.38, cf.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714806
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c029772125594e31eb1a5ad9e0913724ed9891f2
http://kernelnewbies.org/Linux_2_6_38#head-49f5f735853f8cc7c4d89e5c266fe07316b49f4c
Therefore encrypting the array (instead of assembling an array of encrypted
disks) shouldn't cause a performance cost. Also, it makes the ramdisk much
easier to configure :-)
Diffstat (limited to 'src/fripost-postinst-udeb/debian/compat')
0 files changed, 0 insertions, 0 deletions