From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <redwoodhyd@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 44RNqunJckiu for <dm-crypt@saout.de>;
 Fri,  7 Feb 2014 14:51:28 +0100 (CET)
Received: from mail-pb0-x243.google.com (mail-pb0-x243.google.com
 [IPv6:2607:f8b0:400e:c01::243])
 (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,  7 Feb 2014 14:51:28 +0100 (CET)
Received: by mail-pb0-f67.google.com with SMTP id jt11so1172969pbb.10
 for <dm-crypt@saout.de>; Fri, 07 Feb 2014 05:51:26 -0800 (PST)
MIME-Version: 1.0
Date: Fri, 7 Feb 2014 19:21:25 +0530
Message-ID: <CADOhdukb79eGG+BFhpW_54VXJvUoWCAVGF0+EdZqUZD_R7o3hA@mail.gmail.com>
From: Redwood Hyd <redwoodhyd@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [dm-crypt] (no subject)
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

Hi All ,

I did an experimental kernel change in linux/drivers/md/dm-crypt.c for
improving crypto HW performance.
Here is brief of it
static void crypt_io_hints(struct dm_target *ti,
                            struct queue_limits *limits)
{
  limits->physical_block_size = 32768;
  blk_limits_io_min(limits, 32768);
  blk_limits_io_opt(limits, 32768);
}

It works (passed iozone -a,  robocopy from samba client) and doubled
performance of dm-crypt WRITES !

Problem -
After above change cryptsetup luks format started failing disk
validations so additionally in
Cryptsetup-1.1.3  I  did  following changes to pass disk validation:
========================================================
/* Change-1 to overcome validation failure from dm-table.c that
"adding target device  caused an alignment inconsistency"  */
#define LUKS_STRIPES increased from  4000 to 524288

/* Change-2 to overcome validation failure in dm-table.c
"device-mapper: table: 253:1 start=8 not aligned to h/w logical block
size 32768 of dm-0" */
#define LUKS_ALIGN_KEYSLOTS  increased from  4096 to 32768

/* Change-3 Additionally did following change */
#define DEFAULT_ALIGNMENT    increased from  4096 to 32768

Question - Can someone recommend any later  version of cryptsetup
package where I don't need to change
                 cryptsetup and luks format can still pass
validate_hardware_logical_block_alignment() in dm-table.c  for 32k
encrypt block device ?

Performance related changes are experimental - If someone can suggest
things around this I will post my results to forum.

Regards and Thanks in advance
Redwood hyd