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 r8yBSFnTPJUx for <dm-crypt@saout.de>;
 Sat, 15 Oct 2011 21:26:55 +0200 (CEST)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by mail.saout.de (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Sat, 15 Oct 2011 21:26:54 +0200 (CEST)
Message-ID: <4E99DE7A.5070406@redhat.com>
Date: Sat, 15 Oct 2011 21:26:50 +0200
From: Milan Broz <mbroz@redhat.com>
MIME-Version: 1.0
References: <988d796439684f466293e9f526ba6a89.XPN@L622243018051.user.x-privat.org>
In-Reply-To: <988d796439684f466293e9f526ba6a89.XPN@L622243018051.user.x-privat.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] aes-ni
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: Lurkos <lurkos.usenet@gmail.com>
Cc: dm-crypt@saout.de

On 10/15/2011 08:44 PM, Lurkos wrote:
> Does cryptsetup (with luks volumes) support AES-NI for newer Intel and
> AMD powered computers?

yes. (in fact it is cryptoAPI which need proper module loaded, not dmcrypt)
aes-ni has higher priority, so it should be used automatically if available.

btw I just read this
http://www.phoronix.com/scan.php?page=article&item=intel_aesni_dmcrypt

Milan