On 16 March 2017 at 17:42, Nanda Gopal <nandana...@gmail.com> wrote: > Hi Bala, > > > *If your requirement is to support in-place crypto processing you can > specify the output packet* > *as same as input packet (i.e out_pkt = pkt).* > > My requirement is to support out of place, so out_pkt = ODP_PACKET_INVALID? >
Yes. If you keep out_pkt = ODP_PACKET_ INVALID then crypto module will allocate a packet from the output_pool which was configured in the odp_crypto_session_t. If you provide a valid pkt for "out_pkt" then the packet will be encrypted on the out_pkt provided. Regards, Bala > > On Thu, 16 Mar 2017 at 14:01 Bala Manoharan <bala.manoha...@linaro.org> > wrote: > >> >> On 15 March 2017 at 18:42, Nanda Gopal <nandana...@gmail.com> wrote: >> >> *Hi,* >> >> >> >> *When we pass, odp_crypto_op_params_t params to odp_crypto_operation >> >> >> (), as per the documentation, if we set params-> out_pkt to INVALID, a new >> pkt would be created from the original pkt pool, data copied from original >> >> pkt and then passed on to DPDK. * >> >> *In our test case, we are passing a chained buffer to this crypto API, so >> >> >> in order for send the same buffer to lower layer without a copy, are there >> >> any flags to be set? * >> >> >> If your requirement is to support in-place crypto processing you can >> specify the output packet >> as same as input packet (i.e out_pkt = pkt). >> >> Regards, >> Bala >> >> >> >> *Regards,* >> >> *Nanda* >> >> >>
