From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <htd@fancy-poultry.org>
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 C_0v-0MB4S2n for <dm-crypt@saout.de>;
 Tue, 24 Jul 2012 08:11:50 +0200 (CEST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de
 [212.227.126.186]) by mail.saout.de (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Tue, 24 Jul 2012 08:11:50 +0200 (CEST)
Date: Tue, 24 Jul 2012 08:11:48 +0200
From: Heinz Diehl <htd@fancy-poultry.org>
Message-ID: <20120724061148.GA1517@fancy-poultry.org>
References: <20120722190757.GB10089@merlins.org>
 <1342986452.26887.3.camel@scapa>
 <20120722203929.GB3925@merlins.org>
 <20120722214757.GA16793@tansi.org>
 <20120723062850.GA6931@merlins.org>
 <20120723081407.GA872@tansi.org>
 <20120723161242.GB27727@merlins.org> <500D86AC.7090100@redhat.com>
 <20120723175129.GA15867@merlins.org> <500DC2B0.8060409@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <500DC2B0.8060409@redhat.com>
Subject: Re: [dm-crypt] aes-xts-plain with aes_x86_64 makes my SSD 5x slower
 than my encrypted HD
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 24.07.2012, Milan Broz wrote: 

> Disk driver should set topology parameters which fdisk uses. But for your
> case all is set to 512 bytes...

In case of a 4k alignment, I use "fdisk -c -u /dev/sda". The first
partition will start at 2048, and all gets properly aligned as long 
as I'm using "+G" for defining the partitions. The last partition 
on a disk can be misaligned if you choose to use "the rest". Since 
fdisk displays the sectors in an inclusive way, the endsize fdisk is
showing ("p") +1 should be divisible by 8. You can see it the other 
way round and say (endsize MOD 8 = 7). 

It's the same thing with Western Digital and Seagate drives which
use "advanced format". As far as I know, proper alignment is not the
whole thing: some drives doesn't report that they are using the 
new blocksize, and the OS can therefore not know (reporting 512/512
logical/physical blocksize, instead of 512/4096). So the filesystem 
which is created on top of these partitions has to be created using 
the 4096 blocksize: "mkfs.ext4 -b 4096 /dev/sdx", e.g.

I don't know how this is handled via the dmcrypt layer..