From: "Theodore Y. Ts'o" <email@example.com> To: Rob Herring <firstname.lastname@example.org> Cc: AnilKumar Chimata <email@example.com>, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org Subject: Re: [PATCH 3/3] crypto: qce: ice: Add support for Inline Crypto Engine Date: Thu, 25 Oct 2018 11:28:56 -0400 [thread overview] Message-ID: <20181025152856.GD4970@thunk.org> (raw) In-Reply-To: <20181025145548.GA30244@bogus> On Thu, Oct 25, 2018 at 09:55:48AM -0500, Rob Herring wrote: > > +Introduction: > > +============= > > +Storage encryption has been one of the most required feature from security > > +point of view. QTI based storage encryption solution uses general purpose > > +crypto engine. While this kind of solution provide a decent amount of > > +performance, it falls short as storage speed is improving significantly > > +continuously. To overcome performance degradation, newer chips are going to > > +have Inline Crypto Engine (ICE) embedded into storage device. ICE is supposed > > +to meet the line speed of storage devices. > > Is ICE part of the storage device or part of the host as the binding > suggests? My understanding is that for this particular instantiation, the Inline Crypto Engine is located on the SOC. However, from the perspective of generic kernel support, the inline crypto support could be implemented on the SOC, or in the host bus adaptor, or as a "bump in the wire", or on the storage device. And whatever abstract interface in the block layer should be able to support all of these cases. I do not believe it would be wise to assume that inline crypto will forever be a mobile-only thing. I could easily see use cases in the data center; for example, if you believe that Nation State Actors might be trying to create "implants" that attack hard drive firmware, per some of the Snowden leaks, creating an open design ICE engine with auditable firmware and a trusted secure key store, and which sits between the host CPU and the storage device might be one way to mitigate against this threat. - Ted
next prev parent reply other threads:[~2018-10-25 15:29 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-10-17 15:17 [PATCH 0/3] Add Inline Crypto Engine (ICE) driver AnilKumar Chimata 2018-10-17 15:17 ` [PATCH 1/3] firmware: qcom: scm: Update qcom_scm_call signature AnilKumar Chimata 2018-10-17 15:17 ` [PATCH 2/3] dt-bindings: Add ICE device specific parameters AnilKumar Chimata 2018-10-25 18:15 ` Rob Herring 2018-10-29 13:30 ` AnilKumar Chimata 2018-10-17 15:17 ` [PATCH 3/3] crypto: qce: ice: Add support for Inline Crypto Engine AnilKumar Chimata 2018-10-17 17:04 ` Theodore Y. Ts'o 2018-10-24 12:04 ` AnilKumar Chimata 2018-10-17 17:39 ` Randy Dunlap 2018-10-24 14:43 ` AnilKumar Chimata 2018-10-18 11:43 ` kbuild test robot 2018-10-24 11:14 ` anilc 2018-10-25 14:58 ` Rob Herring 2018-10-29 13:31 ` AnilKumar Chimata 2018-10-25 14:55 ` Rob Herring 2018-10-25 15:28 ` Theodore Y. Ts'o [this message] 2018-10-25 15:45 ` Rob Herring 2018-10-29 13:47 ` AnilKumar Chimata
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=20181025152856.GD4970@thunk.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH 3/3] crypto: qce: ice: Add support for Inline Crypto Engine' \ /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
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).