Lines Matching refs:blk_crypto_profile

94 We also introduce ``struct blk_crypto_profile`` to contain all generic inline
96 blk_crypto_profile serves as the way that drivers for inline encryption hardware
99 wants to support inline encryption will construct a blk_crypto_profile, then
102 The blk_crypto_profile also manages the hardware's keyslots, when applicable.
107 Specifically, for each keyslot, the block layer (via the blk_crypto_profile)
166 blk-crypto-fallback also defines its own blk_crypto_profile and has its own
232 blk_crypto_profile in the request_queue of its device.  To do this, it first
237 blk_crypto_profile, e.g. ``modes_supported`` and ``max_dun_bytes_supported``.
240 blk_crypto_profile to tell upper layers how to control the inline encryption
245 Once the driver registers a blk_crypto_profile with a request_queue, I/O
248 the blk_crypto_profile, so drivers don't need to worry about handling
250 blk_crypto_profile, then all I/O requests that have an encryption context will
255 field of the blk_crypto_profile to point to the ``struct device`` that will be
270 encryption need to create their own blk_crypto_profile for their request_queue,
300 (by setting the blk_crypto_profile in the request_queue of the device to NULL).