Hi Thomas, Jerin, Please see inline.
Thanks, Anoob > -----Original Message----- > From: Thomas Monjalon <tho...@monjalon.net> > Sent: Wednesday, December 11, 2019 4:25 AM > To: Jerin Jacob <jerinjac...@gmail.com>; Anoob Joseph > <ano...@marvell.com> > Cc: Akhil Goyal <akhil.go...@nxp.com>; Declan Doherty > <declan.dohe...@intel.com>; Jerin Jacob Kollanukkaran > <jer...@marvell.com>; Narayana Prasad Raju Athreya > <pathr...@marvell.com>; Kiran Kumar Kokkilagadda > <kirankum...@marvell.com>; Nithin Kumar Dabilpuram > <ndabilpu...@marvell.com>; Pavan Nikhilesh Bhagavatula > <pbhagavat...@marvell.com>; Ankur Dwivedi <adwiv...@marvell.com>; > Archana Muniganti <march...@marvell.com>; Tejasree Kondoj > <ktejas...@marvell.com>; Vamsi Krishna Attunuru > <vattun...@marvell.com>; Lukas Bartosik <lbarto...@marvell.com>; dpdk- > dev <dev@dpdk.org> > 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 <ano...@marvell.com> > 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?
