From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 lk6vccw9jLbM for ; Sun, 16 Oct 2011 20:57:03 +0200 (CEST) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mail.saout.de (Postfix) with ESMTP for ; Sun, 16 Oct 2011 20:57:02 +0200 (CEST) Message-ID: <4E9B28F9.1060508@redhat.com> Date: Sun, 16 Oct 2011 20:56:57 +0200 From: Milan Broz MIME-Version: 1.0 References: <988d796439684f466293e9f526ba6a89.XPN@L622243018051.user.x-privat.org> <4E99DE7A.5070406@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] aes-ni List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Lurkos Cc: dm-crypt@saout.de On 10/16/2011 07:21 PM, Lurkos wrote: > Maybe aesni_intel supersedes aes_x86_64 once loaded? yes, see /proc/crypto when modules are loaded and check priorities of aes-ni crypto driver (it should be autoloaded). hw drivers have always higher priority. you can blacklist modules if needed though. (there is no way to select modules through dmcrypt directly) Milan