From: Milan Broz <gmazyland@gmail.com>
To: Pelle Svensson <pelle2004@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] SATA Hardware encryption AES support
Date: Thu, 28 Nov 2013 14:39:22 +0100 [thread overview]
Message-ID: <5297478A.4060000@gmail.com> (raw)
In-Reply-To: <CAFOvWLHJHJmQaAWf4ur=5LXz4wBZhHVZc47qrv_hQCJjJaBuXA@mail.gmail.com>
On 11/28/2013 01:18 PM, Pelle Svensson wrote:
> Hi,
>
> Marvel 88SE9230 SATA controller has AES hardware encryption built-in.
>
> - Will Linux LUKS make use of this if there is support in the kernel driver?
> - If it can't, dose LUKS/dm-crypt by design has any support this type hardware, i.e. can I write a kernel driver?
Short answer - no (for dmcrypt/LUKS).
Encryption on this level is below the dmcrypt layer operates.
So if you need to use this hw layer, you have to modify SATA layer drivers, not dmcrypt.
Milan
prev parent reply other threads:[~2013-11-28 13:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 12:18 [dm-crypt] SATA Hardware encryption AES support Pelle Svensson
2013-11-28 13:39 ` Milan Broz [this message]
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=5297478A.4060000@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=pelle2004@gmail.com \
/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