From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mail.saout.de (Postfix) with ESMTP for ; Thu, 2 Dec 2010 13:08:32 +0100 (CET) Message-ID: <4CF78C3B.1010809@redhat.com> Date: Thu, 02 Dec 2010 13:08:27 +0100 From: Milan Broz MIME-Version: 1.0 References: <20101201145123.GA10238@dentifrice> <20101202075413.GE19274@maude.comedia.it> <20101202114038.GA3149@dentifrice> In-Reply-To: <20101202114038.GA3149@dentifrice> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] status of dm-crypt (alignment issues) on a SSD List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: mike dentifrice Cc: dm-crypt@saout.de On 12/02/2010 12:50 PM, mike dentifrice wrote: > So far, everything seems good as far as I understnad, but should > `cryptsetup` have 'queue' strings as well ? Mine (v1.1.3) doesn't. I > compiled 1.2.0-rc1 and it doesn't either. Is that a stopper of not? Grepping for queue is not clever idea, sorry. 1.1.3 has topology support, 1.2.0 adds 1MiB default here. Run luksFormat --debug and you will see topology info read from kernel: # Topology: IO (512/0), offset = 0; Required alignment is 4096 bytes. 512/0, offset = 0 means min io size / opt io size and offset from sysfs. For ssd it should be surenly not 512 but something like write block. Milan