From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail.saout.de ([127.0.0.1])
 by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id QGuNTZWLESBz for <dm-crypt@saout.de>;
 Fri, 23 Nov 2012 10:43:02 +0100 (CET)
Received: from mail-ee0-f50.google.com (mail-ee0-f50.google.com [74.125.83.50])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mail.saout.de (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Fri, 23 Nov 2012 10:43:02 +0100 (CET)
Received: by mail-ee0-f50.google.com with SMTP id b45so4759627eek.37
 for <dm-crypt@saout.de>; Fri, 23 Nov 2012 01:43:02 -0800 (PST)
Message-ID: <50AF4523.9010709@gmail.com>
Date: Fri, 23 Nov 2012 10:42:59 +0100
From: Milan Broz <gmazyland@gmail.com>
MIME-Version: 1.0
References: <50AEF7B3.4000807@babioch.de> <20121123060720.GA5520@tansi.org>
 <50AF3B3F.9000508@gmail.com> <20121123092740.GA15419@tansi.org>
In-Reply-To: <20121123092740.GA15419@tansi.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] Reconsidering default options for
	cryptsetup-reencrypt
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

On 11/23/2012 10:27 AM, Arno Wagner wrote:
>> Also there are SSD drives which uses internally RAID0 to speed
>> up operations (in reality it is more independent SSD drives inside).
> 
> Ok, but I think _that_ does not count, unless you know of some
> that expose the controller. ;-)

just FYI
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=99a700bcc75429ba84a672d04f0b650dcc5b3042

All these drives in manline linux (with patch above) are visible as separate devices
(separate controllers) while with proprietary driver you see one big device
(which is raid0 internally in fact)

I was able to mount it with mdadm with 64k chunk size later (with separate drives).

Its fw seems to be optimized for the raid0 case though...

Milan