Re: [RFC v2 2/3] crypto: Introduce CRYPTO_ALG_BULK flag
From: Baolin Wang
Date: Fri Jun 03 2016 - 02:48:41 EST
On 2 June 2016 at 16:26, Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> wrote:
> On Fri, May 27, 2016 at 07:11:23PM +0800, Baolin Wang wrote:
>> Now some cipher hardware engines prefer to handle bulk block rather than one
>> sector (512 bytes) created by dm-crypt, cause these cipher engines can handle
>> the intermediate values (IV) by themselves in one bulk block. This means we
>> can increase the size of the request by merging request rather than always 512
>> bytes and thus increase the hardware engine processing speed.
>> So introduce 'CRYPTO_ALG_BULK' flag to indicate this cipher can support bulk
>> Signed-off-by: Baolin Wang <baolin.wang@xxxxxxxxxx>
> I think a better aproach would be to explicitly move the IV generation
> into the crypto API, similar to how we handle IPsec. Once you do
> that then every algorithm can be handled through the bulk interface.
Sorry for late reply.
If we move the IV generation into the crypto API, we also can not
handle every algorithm with the bulk interface. Cause we also need to
use different methods to map one whole bio or map one sector according
to the algorithm whether can support bulk mode or not. Please correct
me if I misunderstand your points. Thanks.
> Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
> Home Page: http://gondor.apana.org.au/~herbert/
> PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt