Re: [PATCH v3 4/4] crypto: add CRYPTO_TFM_REQ_IV_SERIALIZE flag

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

 



Am Sonntag, 18. Februar 2018, 15:25:27 CET schrieb Gilad Ben-Yossef:

Hi Gilad,

> On Sat, Feb 10, 2018 at 12:04 AM, Stephan Müller <smueller@xxxxxxxxxx> 
wrote:
> > Crypto drivers may implement a streamlined serialization support for AIO
> > requests that is reported by the CRYPTO_ALG_SERIALIZES_IV_ACCESS flag to
> > the crypto user. When the user decides that he wants to send multiple
> > AIO requests concurrently and wants the crypto driver to handle the
> > serialization, the caller has to set CRYPTO_TFM_REQ_IV_SERIALIZE to notify
> > the crypto driver.
> > 
> > Only when this flag is enabled, the crypto driver shall apply its
> > serialization logic for handling IV updates between requests. If this
> > flag is not provided, the serialization logic shall not be applied by
> > the driver as the caller decides that it does not need it (because no
> > parallel AIO requests are sent) or that it performs its own
> > serialization.
> 
> Tested and it is working with the ccree driver which supports IV
> serialization.
> 
> Tested-by: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>

Thank you.
> 
> Gilad



Ciao
Stephan






[Index of Archives]     [Kernel]     [Gnu Classpath]     [Gnu Crypto]     [DM Crypt]     [Netfilter]     [Bugtraq]

  Powered by Linux