Hi Thomas, Jerin, Please see inline.
Thanks, Anoob > -----Original Message----- > From: Thomas Monjalon <[email protected]> > Sent: Wednesday, December 11, 2019 4:25 AM > To: Jerin Jacob <[email protected]>; Anoob Joseph > <[email protected]> > Cc: Akhil Goyal <[email protected]>; Declan Doherty > <[email protected]>; Jerin Jacob Kollanukkaran > <[email protected]>; Narayana Prasad Raju Athreya > <[email protected]>; Kiran Kumar Kokkilagadda > <[email protected]>; Nithin Kumar Dabilpuram > <[email protected]>; Pavan Nikhilesh Bhagavatula > <[email protected]>; Ankur Dwivedi <[email protected]>; > Archana Muniganti <[email protected]>; Tejasree Kondoj > <[email protected]>; Vamsi Krishna Attunuru > <[email protected]>; Lukas Bartosik <[email protected]>; dpdk- > dev <[email protected]> > Subject: [EXT] Re: [dpdk-dev] [PATCH 00/15] add OCTEONTX2 inline IPsec > support > > External Email > > ---------------------------------------------------------------------- > 09/12/2019 09:06, Jerin Jacob: > > On Sun, Dec 8, 2019 at 5:25 PM Anoob Joseph <[email protected]> > wrote: > > > > > > This series adds inline IPsec support in OCTEONTX2 PMD. > > > > > > In the inbound path, rte_flow framework need to be used to configure > > > the NPC block, which does the h/w lookup. The packets would get > > > processed by the crypto block and would submit to the scheduling > > > block, SSO. So inline IPsec mode can be enabled only when traffic is > > > received via event device using Rx adapter. > > > > > > In the outbound path, the core would submit to the crypto block and > > > the crypto block would submit the packet for Tx internally. > > > > > > > The release note update is missing. > [Anoob] Will update in v2. > Yes, and the MAINTAINERS file as well. [Anoob] The required files are added in crypto/octeontx2 directory, which already specifies the maintainers. Do we need inline ipsec mentioned separately?
