From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mbroz@redhat.com>
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, 26 Feb 2011 11:18:55 +0100 (CET)
Message-ID: <4D68D38B.9010600@redhat.com>
Date: Sat, 26 Feb 2011 11:18:51 +0100
From: Milan Broz <mbroz@redhat.com>
MIME-Version: 1.0
References: <AANLkTin9dq8f3_Y9vhyo+YQBCXP6C7OiY8+uZxu=KAMr@mail.gmail.com>
In-Reply-To: <AANLkTin9dq8f3_Y9vhyo+YQBCXP6C7OiY8+uZxu=KAMr@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] hardware encryption question
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: Chuck Tuffli <ctuffli@gmail.com>
Cc: dm-crypt@saout.de

On 02/26/2011 12:35 AM, Chuck Tuffli wrote:
> I'm developing a device driver for a SCSI card that is able to do
> XTS-AES encryption as a part of IO. Is it possible for dm-crypt to
> take advantage of this encryption offload? If not, what would I need
> to change to enable this capability? TIA!

dm-crypt uses kernel cryptoAPI, so if you implement proper driver
for cryptoAPI and this driver will be primary (or automatically detected)
for the cipher/mode it will be used in dm-crypt.

But it if it is not able to separate encryption from io path, you
cannot use it in dm-crypt. But you can stack other block devices over it
(like LVM).

Milan