From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 9324C41BDC; Sun, 5 Feb 2023 17:14:06 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2D45540A89; Sun, 5 Feb 2023 17:14:06 +0100 (CET) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by mails.dpdk.org (Postfix) with ESMTP id 7C27040A7D for ; Sun, 5 Feb 2023 17:14:04 +0100 (CET) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 1A0FE5C0228; Sun, 5 Feb 2023 11:14:02 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Sun, 05 Feb 2023 11:14:02 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm3; t=1675613642; x= 1675700042; bh=VrwE1Tz6wYvrCde0f+yOq8j7anxqlXNggvfKPkcTHCQ=; b=g K5NiEf+z1UPQtMjXO6L/hJ281mJGNdtZj6ZNvwdZQop0moCWNMzB0CKCeerYsEac ZwIqm1upFhMoJQC3hHX7z5khkfaveFOH7HaR5CJWetvXO0nAR8kCxCIY9KK3Ko2h wU1Ct3JCMFfInR++gHptf/qDhXVu+6TZrRR40IRepvor0YQn6/ma5pIWOt9zqF6y oACUtaUBjIkhc4yT8LEgnhq8OhTFTLfEzzgOofMssN09vuTwzf9kNRQxH3Ub/C3x nNVLPZPJLM6UtoYu/bx2shbZIjDjUXFMqak9vSALMdKCTnrXKY2Vtn3KoaVs2AR7 DV2PDKSPtrMcpvaClqxBw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1675613642; x= 1675700042; bh=VrwE1Tz6wYvrCde0f+yOq8j7anxqlXNggvfKPkcTHCQ=; b=s 60BQn4E3PWP/wzELbsGrTUgBPnp3CS4PPdB91wd7nZxMK7ZA/ICv1N6zsZ2Uc39f Hx5fYYR3GuzkU82IDArzAlv4Futa7w6Hh9Cq5SscNJCiTEmcLxqsqaKou17jLLdz 3kksFc2MzCG/uwnLxyZx0fO5T02OnvDuNeEJ7G9o8uIvTkRKag5y7YoN7nihIRue gwWK9N/RuL1tUH/16T1gTryfBwX3bBaLqeImQINSyXEQTwdXiTjYQlROUyItaJv5 jQo9+kYX7O5jm0WQce5OuC8JKKMbNi5ThcwdVpT8NOdRovAHgPZDEugmnJrsKtLR BBnsY1fKLfLohetm8RMaA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudeggedgkeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpedtjeeiieefhedtfffgvdelteeufeefheeujefgueetfedttdei kefgkeduhedtgfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 5 Feb 2023 11:14:00 -0500 (EST) From: Thomas Monjalon To: Cristian Dumitrescu Cc: dev@dpdk.org Subject: Re: [PATCH V6 00/11] pipeline: add IPsec support Date: Sun, 05 Feb 2023 17:13:58 +0100 Message-ID: <4243983.ejJDZkT8p0@thomas> In-Reply-To: <20230126141256.380415-1-cristian.dumitrescu@intel.com> References: <20230111205608.87953-1-cristian.dumitrescu@intel.com> <20230126141256.380415-1-cristian.dumitrescu@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 26/01/2023 15:12, Cristian Dumitrescu: > This patch set introduces a companion block for the SWX pipeline for > IPsec support. > > The IPsec block is external to the pipeline, hence it needs to be > explicitly instantiated by the user and connected to a pipeline > instance through the pipeline I/O ports. > > Main features: > * IPsec inbound (encrypted input packets -> clear text output packets) > and outbound (clear text input packets -> encrypted output packets) > processing support for tunnel and transport modes. > > Interaction of the IPsec block with the pipeline: > * Each IPsec block instance has its own set of Security Associations > (SAs) used to process the input packets. Each SA is identified by its > unique SA ID. The IPsec inbound and outbound SAs share the same ID > space. > * Each input packet is first mapped to one of the existing SAs by > using the SA ID and then processed according to the identified SA. The > SA ID is read from input packet. The SA ID field is typically written > by the pipeline before sending the packet to the IPsec block. Applied, thanks.