From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 681971B017 for ; Tue, 16 Jan 2018 12:01:15 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Jan 2018 03:01:13 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,368,1511856000"; d="scan'208";a="10780666" Received: from irsmsx152.ger.corp.intel.com ([163.33.192.66]) by fmsmga008.fm.intel.com with ESMTP; 16 Jan 2018 03:01:12 -0800 Received: from irsmsx104.ger.corp.intel.com ([169.254.5.248]) by IRSMSX152.ger.corp.intel.com ([169.254.6.87]) with mapi id 14.03.0319.002; Tue, 16 Jan 2018 11:00:57 +0000 From: "Nicolau, Radu" To: Anoob Joseph , Akhil Goyal , "Doherty, Declan" , "Gonzalez Monroy, Sergio" CC: Jerin Jacob , Narayana Prasad , "dev@dpdk.org" Thread-Topic: [PATCH v6 2/2] examples/ipsec-secgw: add support for inline protocol Thread-Index: AQHTd9AKg38Ld4DW0EuXcx34GIGwt6N2gtrg Date: Tue, 16 Jan 2018 11:00:56 +0000 Message-ID: <763A2F19A5EFF34F8B7F1657C992EE297B30E790@IRSMSX104.ger.corp.intel.com> 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-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYmYxYjNjZDEtZjBlYS00ZDUyLThkYjUtMTYxNWE5YWNmMmUzIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6Iko4a29sTWpmWFVJczk5ZkRVajF3d0hnZlwvWFNlaWhVSzNrcWxpc3krb0xFPSJ9 dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [163.33.239.182] 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: Tue, 16 Jan 2018 11:01:16 -0000 > -----Original Message----- > From: Anoob Joseph [mailto:anoob.joseph@caviumnetworks.com] > 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: [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 pa= cket > will have optional metadata, which could be used to identify the security > session associated with the packet. >=20 > Signed-off-by: Anoob Joseph > --- Acked-by: Radu Nicolau