From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mbroz@redhat.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 l-t5lKGsTTz7 for <dm-crypt@saout.de>;
 Thu, 12 Jan 2012 16:23:02 +0100 (CET)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by mail.saout.de (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Thu, 12 Jan 2012 16:23:01 +0100 (CET)
Received: from int-mx12.intmail.prod.int.phx2.redhat.com
 (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25])
 by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q0CFN0f8026371
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
 for <dm-crypt@saout.de>; Thu, 12 Jan 2012 10:23:00 -0500
Received: from [10.36.6.232] (vpn1-6-232.ams2.redhat.com [10.36.6.232])
 by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id
 q0CFMx9W010987
 for <dm-crypt@saout.de>; Thu, 12 Jan 2012 10:23:00 -0500
Message-ID: <4F0EFAD3.3090908@redhat.com>
Date: Thu, 12 Jan 2012 16:22:59 +0100
From: Milan Broz <mbroz@redhat.com>
MIME-Version: 1.0
References: <20120112150640.GA1918@fancy-poultry.org>
In-Reply-To: <20120112150640.GA1918@fancy-poultry.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] Twofish 3-way
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 01/12/2012 04:06 PM, Heinz Diehl wrote:
> Hi,
>
> since kernel 3.2 there is a new parallelized variant of twofish
> available via
>
> CONFIG_CRYPTO_TWOFISH_X86_64_3WAY
>
> How can I use it with LUKS/dmcrypt? My current config contains the
> following:
>
> # CONFIG_CRYPTO_TWOFISH is not set
> CONFIG_CRYPTO_TWOFISH_COMMON=y
> CONFIG_CRYPTO_TWOFISH_X86_64=y
> CONFIG_CRYPTO_TWOFISH_X86_64_3WAY=y
>
> How should these options be set up properly?

You cannot set directly which version is used through dmcrypt interface,
(without patching kernel source) but cryptoAPI should detect the fastest
algorithm automatically.

For separate modules, force load just that module and unload all other
should perhaps work as well (before crypto device activation).

(see /proc/crypto and lsmod modules reference count to check which one
is really used)

Milan