From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id 706DF1B171 for ; Mon, 8 Jan 2018 17:11:04 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Jan 2018 08:11:03 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,330,1511856000"; d="scan'208";a="8074066" Received: from irsmsx106.ger.corp.intel.com ([163.33.3.31]) by fmsmga007.fm.intel.com with ESMTP; 08 Jan 2018 08:11:01 -0800 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.167]) by IRSMSX106.ger.corp.intel.com ([169.254.8.36]) with mapi id 14.03.0319.002; Mon, 8 Jan 2018 16:11:00 +0000 From: "De Lara Guarch, Pablo" To: Anoob Joseph , Akhil Goyal , "Doherty, Declan" , "Nicolau, Radu" , "Gonzalez Monroy, Sergio" CC: Jerin Jacob , Narayana Prasad , "dev@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH v6 2/2] examples/ipsec-secgw: add support for inline protocol Thread-Index: AQHTd9ATUNJr5PSLq0OdTFlp2JDDg6NqRrHA Date: Mon, 8 Jan 2018 16:10:59 +0000 Message-ID: References: <1513327396-22178-1-git-send-email-anoob.joseph@caviumnetworks.com> <1513581305-26202-1-git-send-email-anoob.joseph@caviumnetworks.com> <1513581305-26202-3-git-send-email-anoob.joseph@caviumnetworks.com> In-Reply-To: <1513581305-26202-3-git-send-email-anoob.joseph@caviumnetworks.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiOTA5YTVjMWItNzAwYS00ZDM2LWE0YTYtY2ZmODAwYjM3ZDdlIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6IklMYzRRUmNEMGdjZTZoMTZYbjVrdlRcL3lMTFFVSjZ5a0dFV05Yb3pOZzlrPSJ9 x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v6 2/2] examples/ipsec-secgw: add support for inline protocol X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 16:11:04 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Anoob Joseph > Sent: Monday, December 18, 2017 7:15 AM > To: Akhil Goyal ; Doherty, Declan > ; Nicolau, Radu ; > Gonzalez Monroy, Sergio > Cc: Anoob Joseph ; Jerin Jacob > ; Narayana Prasad > ; dev@dpdk.org > Subject: [dpdk-dev] [PATCH v6 2/2] examples/ipsec-secgw: add support for > inline protocol >=20 > Adding support for inline protocol processing >=20 > In ingress side, application will receive regular IP packets, without any= IPsec > related info. Application will do a selector check (SP-SA > check) by making use of the metadata from the packet. The device-specific > metadata in mbuf would aid in determing the security session which > processed the packet. >=20 > In egress side, the plain packet would be submitted to the driver. The > packet will have optional metadata, which could be used to identify the > security session associated with the packet. >=20 > Signed-off-by: Anoob Joseph Akhil, Radu, could you review this patch? Thanks, Pablo