On 21-01-2018 17:44, Stephan Müller wrote: > Hi Herbert, > > I tried to summarize the use cases of the AIO support at [1]. > > The use case covering the inline IV support is documented in section [2]. It > naturally would depend on this patch to be accepted. What is your take on this > use case? > > What is your take on the issue outlined at [3]? Should the affected drivers be > updated? Till now driver is using content of req->info as IV for cipher operation and It treats each request independent of previous request. >From description given at [1]. Following is the new requirement for Driver. "The cipher implementations ensure that although the IOVECs cause parallel invocation of the recvmsg handler, they are serialized such that the one IV sent to the kernel is updated by the first cipher operation and used as input to the second cipher operation, and so on. This implies, for example, that the CBC block chaining operation is applied for all IOVECs." To make this work how driver will know that it has to delay the processing of current request because previous request is not complete(or IV is not available) . > Thanks > Stephan > > [1] https://github.com/smuellerDD/libkcapi/commit/ > 29132075b8f045f3f92367c0190add81ccf5da11 > > [2] https://github.com/smuellerDD/libkcapi/commit/ > 29132075b8f045f3f92367c0190add81ccf5da11#diff- > dce7a00cbc610df94f0dc27eb769d01dR644 > > [3] https://github.com/smuellerDD/libkcapi/commit/ > 29132075b8f045f3f92367c0190add81ccf5da11#diff- > dce7a00cbc610df94f0dc27eb769d01dR575 > >
