From: Milan Broz <mbroz@redhat.com>
To: Chuck Tuffli <ctuffli@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] hardware encryption question
Date: Sat, 26 Feb 2011 11:18:51 +0100 [thread overview]
Message-ID: <4D68D38B.9010600@redhat.com> (raw)
In-Reply-To: <AANLkTin9dq8f3_Y9vhyo+YQBCXP6C7OiY8+uZxu=KAMr@mail.gmail.com>
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
next prev parent reply other threads:[~2011-02-26 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 23:35 [dm-crypt] hardware encryption question Chuck Tuffli
2011-02-26 10:18 ` Milan Broz [this message]
2011-03-03 1:28 ` Chuck Tuffli
2011-03-09 10:34 ` Milan Broz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D68D38B.9010600@redhat.com \
--to=mbroz@redhat.com \
--cc=ctuffli@gmail.com \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox