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 hnf9njTam0ri for <dm-crypt@saout.de>;
 Thu, 28 Nov 2013 15:51:35 +0100 (CET)
Received: from mail-ea0-x22a.google.com (mail-ea0-x22a.google.com
 [IPv6:2a00:1450:4013:c01::22a])
 (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>; Thu, 28 Nov 2013 15:51:35 +0100 (CET)
Received: by mail-ea0-f170.google.com with SMTP id k10so6024157eaj.1
 for <dm-crypt@saout.de>; Thu, 28 Nov 2013 06:51:35 -0800 (PST)
Message-ID: <52975873.1010009@gmail.com>
Date: Thu, 28 Nov 2013 15:51:31 +0100
From: Milan Broz <gmazyland@gmail.com>
MIME-Version: 1.0
References: <b1bf0a8a357ca9ddcafcfeccdd4f1d6e@madez.de>
In-Reply-To: <b1bf0a8a357ca9ddcafcfeccdd4f1d6e@madez.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] REQUIRED CIPHERS TEST takes 20 minutes each for
 aes-related ciphers
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: christian@madez.de
Cc: dm-crypt@saout.de

On 11/28/2013 02:25 PM, christian@madez.de wrote:
> Hello,
> 
> I just compiled cryptsetup-1.6.2 on a machine with AES-NI. During the
> compilation there were some tests. The lines of the output when the
> issue occurred were:
> 
> REQUIRED CIPHERS TEST
> #  Algorithm | Key |  Encryption |  Decryption
>       aes-cbc   256b   975.0 MiB/s  2037065.0 MiB/s
>       aes-lrw   384b  103909.0 MiB/s  158691.0 MiB/s
>       aes-xts   512b  1731833.0 MiB/s  1681613.0 MiB/s

Wow :) This is apparently bug somewhere.

Can you please sent me (or better create new issue
http://code.google.com/p/cryptsetup/issues/entry)

Please attach cryptsetup benchmark with --debug,
lsmod, cat /proc/crypto and uname -a.
(I will probably need more info later though...)

Thanks!
Milan