From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 578FBA04B3; Fri, 13 Dec 2019 11:18:12 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 0D5852B93; Fri, 13 Dec 2019 11:18:11 +0100 (CET) Received: from new1-smtp.messagingengine.com (new1-smtp.messagingengine.com [66.111.4.221]) by dpdk.org (Postfix) with ESMTP id 69E1B1D9E for ; Fri, 13 Dec 2019 11:18:09 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailnew.nyi.internal (Postfix) with ESMTP id 91F9B5FC6; Fri, 13 Dec 2019 05:18:08 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 13 Dec 2019 05:18:08 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=bHu9Q/oWqZnEM2s4bqTLRvkodAqLNXn7BNtG7cDabvE=; b=djJoeQfd/L2D pMYMvS5ZDBmybD11ad62pNBFN//v/gtx84PbZZo8YtAvJz27u+//APlmaawTjM6I 0vJjvNgzBWZsFotffHT36ZQA6e/cRMKsVnGT4AfYcDyONBJ30KgJCF+xkBxHiKp8 TD8fEUO4K5SlVxwN0gw9DdLw/XjNEb4= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=bHu9Q/oWqZnEM2s4bqTLRvkodAqLNXn7BNtG7cDab vE=; b=HK5VGKP9TFMcy/J/U59WZkqDsZTJ1r818QDrVRqxZdVL0PsJnxE7WG2Rk ma4BSk5rzigzbFo97tqLKAmXwfBCdQzCA8iSlz3T/MZQx4qER9ggI+8gPvwo9fgi JbH+2YRdeXSCUVsoO65otyiDPpqu3dxQ/exveHsbHX6XcigyxWPQrIYIplNrGpUB u/04E+UkO4sqwq1Nw9g2RJOTQmJGyFif4Z7utmVmRjagK6G0pVbHiDvxAfe0ja1s vhr9yB1KZX07tv4QUa+PA7tZXD2ghtRhxN195ty+KytS50W9d4gdJ+G5oCZypLB/ 3XMCliKM7ueakg6gbt193WDSUBA3A== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudelledgudegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 5988680066; Fri, 13 Dec 2019 05:18:06 -0500 (EST) From: Thomas Monjalon To: Anoob Joseph Cc: Jerin Jacob , Akhil Goyal , Declan Doherty , Jerin Jacob Kollanukkaran , Narayana Prasad Raju Athreya , Kiran Kumar Kokkilagadda , Nithin Kumar Dabilpuram , Pavan Nikhilesh Bhagavatula , Ankur Dwivedi , Archana Muniganti , Tejasree Kondoj , Vamsi Krishna Attunuru , Lukas Bartosik , dpdk-dev Date: Fri, 13 Dec 2019 11:18:04 +0100 Message-ID: <3465072.Pq32deZV5p@xps> In-Reply-To: References: <1575806094-28391-1-git-send-email-anoobj@marvell.com> <7036622.ikHXUKB4M3@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [EXT] Re: [PATCH 00/15] add OCTEONTX2 inline IPsec support 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 13/12/2019 08:41, Anoob Joseph: > Hi Thomas, Jerin, > > Please see inline. > > Thanks, > Anoob > > From: Thomas Monjalon > > 09/12/2019 09:06, Jerin Jacob: > > > On Sun, Dec 8, 2019 at 5:25 PM Anoob Joseph > > 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? No sorry, it's fine.