• Home
  • Raw
  • Download

Lines Matching full:hardware

10 Inline encryption hardware sits logically between memory and the disk, and can
11 en/decrypt data as it goes in/out of the disk. Inline encryption hardware has a
16 the inline encryption hardware will en/decrypt the data in the request with the
28 IE hardware is absent. We also want IE to work with layered devices
29 like dm and loopback (i.e. we want to be able to use the IE hardware
37 - IE hardware has a limited number of "keyslots" that can be programmed
60 While IE hardware works on the notion of keyslots, the FS layer has no
65 encryption contexts specified by the FS to keyslots on the IE hardware.
66 This KSM also serves as the way IE hardware can expose its capabilities to
94 blissfully unaware of whether or not real inline encryption hardware is present
113 Regardless of whether real inline encryption hardware is used or the
115 on-disk format of data) will be the same (assuming the hardware's implementation
118 If a ``request queue``'s inline encryption hardware claimed to support the
154 blk-crypto-fallback, if hardware support isn't available for the desired
160 (either by real inline encryption hardware, or by the blk-crypto-fallback).
162 wants to use an algorithm that may not supported by hardware - this function
169 hardware supports the key's crypto settings, or the crypto API fallback has
178 inline encryption hardware that the key might have been programmed into (or the blk-crypto-fallback…
186 keyslots supported by the hardware.
189 IE hardware in the device to do things like programming the crypto key into
190 the IE hardware into a particular keyslot. All this is achieved through the
195 (e.g. when it wants to program a crypto key into the IE hardware, the device
238 At the time of this patch, there is no real hardware that supports both these
251 that it changes the on disk format depending on whether hardware inline
256 Because there isn't any real hardware yet, it seems prudent to assume that
257 hardware implementations might not implement both features together correctly,
259 kernel will pretend that the device does not support hardware inline encryption