Re: [RFC 2/3] crypto: Introduce CRYPTO_ALG_BULK flag

On 27 May 2016 at 15:53, Milan Broz wrote: > On 05/27/2016 09:04 AM, Baolin Wang wrote: >> Hi Milan, >> >> On 27 May 2016 at 14:31, Milan Broz wrote: >>> On 05/25/2016 08:12 AM, Baolin Wang wrote: Now some cipher hardware engines prefer to handle

Re: [RFC 2/3] crypto: Introduce CRYPTO_ALG_BULK flag

On 27 May 2016 at 15:53, Milan Broz wrote: > On 05/27/2016 09:04 AM, Baolin Wang wrote: >> Hi Milan, >> >> On 27 May 2016 at 14:31, Milan Broz wrote: >>> On 05/25/2016 08:12 AM, Baolin Wang wrote: Now some cipher hardware engines prefer to handle bulk block rather than one sector

Re: [RFC 2/3] crypto: Introduce CRYPTO_ALG_BULK flag

On 05/27/2016 09:04 AM, Baolin Wang wrote: > Hi Milan, > > On 27 May 2016 at 14:31, Milan Broz wrote: >> On 05/25/2016 08:12 AM, Baolin Wang wrote: >>> Now some cipher hardware engines prefer to handle bulk block rather than one >>> sector (512 bytes) created by dm-crypt,

Re: [RFC 2/3] crypto: Introduce CRYPTO_ALG_BULK flag

On 05/27/2016 09:04 AM, Baolin Wang wrote: > Hi Milan, > > On 27 May 2016 at 14:31, Milan Broz wrote: >> On 05/25/2016 08:12 AM, 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

Re: [RFC 2/3] crypto: Introduce CRYPTO_ALG_BULK flag

Hi Milan, On 27 May 2016 at 14:31, Milan Broz wrote: > On 05/25/2016 08:12 AM, 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

Re: [RFC 2/3] crypto: Introduce CRYPTO_ALG_BULK flag

Hi Milan, On 27 May 2016 at 14:31, Milan Broz wrote: > On 05/25/2016 08:12 AM, 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

Re: [RFC 2/3] crypto: Introduce CRYPTO_ALG_BULK flag

On 05/25/2016 08:12 AM, 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

Re: [RFC 2/3] crypto: Introduce CRYPTO_ALG_BULK flag

On 05/25/2016 08:12 AM, 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

[RFC 2/3] crypto: Introduce CRYPTO_ALG_BULK flag

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

[RFC 2/3] crypto: Introduce CRYPTO_ALG_BULK flag

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