On 21.06.2017 14:48, Dmitry Eremin-Solenikov wrote: > Input and output of crypto operations are packets. API is more flexible > for application and API pipelining when output is packet with additional > metadata. Application or API pipeline stages which do not care about > crypto results may work on basic packet metadata. > > Crypto result event type changes from ODP_EVENT_CRYPTO_COMPL to > ODP_EVENT_PACKET. Event subtype (ODP_EVENT_PACKET_CRYPTO) can be > used to identify packets with crypto metadata. > > Signed-off-by: Dmitry Eremin-Solenikov <dmitry.ereminsoleni...@linaro.org> > --- > This depends on all previous patches related to IPsec and event types.
This RFC was posted mostly to consult wrt: - split single API call to two for SYNC and ASYNC operation This is to follow IPsec lead. - behaviour wrt in_place decoding: Currently we have per-operation option of specifying output packet (and allocating from pool if INVALID packet was provided). This patch provides same behaviour for SYNC operation and always reuses packet for ASYNC operation. Another option can be: allocate new packet if pool was provided, reuse packet if no pool was provided. To provide fine-grained control, it might be feasible to move pool to crypto_op_param instead of crypto_session_param. -- With best wishes Dmitry
