Re: [PATCH v7 3/9] block: blk-crypto-fallback for Inline Encryption

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Satya Tangirala <satyat@xxxxxxxxxx>
Subject: Re: [PATCH v7 3/9] block: blk-crypto-fallback for Inline Encryption
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Fri, 21 Feb 2020 09:35:39 -0800
In-reply-to: <20200221115050.238976-4-satyat@google.com>
References: <20200221115050.238976-1-satyat@google.com> <20200221115050.238976-4-satyat@google.com>

High-level question:  Does the whole keyslot manager concept even make
sense for the fallback?  With the work-queue we have item that exectutes
at a time per cpu.  So just allocatea per-cpu crypto_skcipher for
each encryption mode and there should never be a slot limitation.  Or
do I miss something?

Follow-Ups:
- Re: [PATCH v7 3/9] block: blk-crypto-fallback for Inline Encryption
  - From: Eric Biggers

References:
- [PATCH v7 0/9] Inline Encryption Support
  - From: Satya Tangirala
- [PATCH v7 3/9] block: blk-crypto-fallback for Inline Encryption
  - From: Satya Tangirala

Prev by Date: Re: [PATCH v7 1/9] block: Keyslot Manager for Inline Encryption
Next by Date: Re: [PATCH v7 6/9] scsi: ufs: Add inline encryption support to UFS
Previous by thread: Re: [PATCH v7 3/9] block: blk-crypto-fallback for Inline Encryption
Next by thread: Re: [PATCH v7 3/9] block: blk-crypto-fallback for Inline Encryption
Index(es):
- Date
- Thread

[Index of Archives] [linux Cryptography] [Asterisk App Development] [PJ SIP] [Gnu Gatekeeper] [IETF Sipping] [Info Cyrus] [ALSA User] [Fedora Linux Users] [Linux SCTP] [DCCP] [Gimp] [Yosemite News] [Deep Creek Hot Springs] [Yosemite Campsites] [ISDN Cause Codes]

Powered by Linux