linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: dhowells@redhat.com, linux-fsdevel@vger.kernel.org,
	lsf-pc@lists.linux-foundation.org
Subject: Re: [LSF/MM TOPIC] Inline encryption support for block devices
Date: Fri, 06 Jan 2017 22:29:09 +0000	[thread overview]
Message-ID: <12132.1483741749@warthog.procyon.org.uk> (raw)
In-Reply-To: <20161216173219.rbh6scyk3kpd6by6@thunk.org>

Theodore Ts'o <tytso@mit.edu> wrote:

> Many embedded SOC's are using in-line encryption engines (ICE) to
> accelerate encryption to storage devices.  The way they work is that
> the ICE unit is located between the memory and the flash or other
> storage device, and when the OS submits the I/O, it includes an
> encryption key identifier, indicating which key (out of a small number
> that have been loaded into the ICE hardware) should be used.  The
> hardware then takes care of doing the encryption without needing to
> keep the CPU busy doing the encryption, and without needing to use
> bounce buffers when writing encrypted blocks.

I would be interested in joining this discussion as I've been working on
keyrings and crypto facilities inside the kernel.

David

  reply	other threads:[~2017-01-06 22:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-16 17:32 [LSF/MM TOPIC] Inline encryption support for block devices Theodore Ts'o
2017-01-06 22:29 ` David Howells [this message]
2017-01-24 22:55   ` Michael Halcrow
2017-01-24 23:16     ` [Lsf-pc] " James Bottomley
2017-01-12 13:36 ` Lukas Czerner
2017-01-12 16:58   ` Theodore Ts'o

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=12132.1483741749@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).