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 5A52A45700 for ; Wed, 31 Jul 2024 12:45:39 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9064B40E64; Wed, 31 Jul 2024 12:45:35 +0200 (CEST) Received: from fout6-smtp.messagingengine.com (fout6-smtp.messagingengine.com [103.168.172.149]) by mails.dpdk.org (Postfix) with ESMTP id C7EC240696; Wed, 31 Jul 2024 12:39:33 +0200 (CEST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailfout.nyi.internal (Postfix) with ESMTP id 50D3113823A1; Wed, 31 Jul 2024 06:39:33 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Wed, 31 Jul 2024 06:39:33 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm3; t=1722422373; x=1722508773; bh=GHJ3FYAOhn+I0/+mFW/l1foRVbkKVNCSpEnXb9LzW8U=; b= DRLA2UqaE9xbEz9sU1EI8TC5sPXkZvOSv3DY+p8ZgJE+ya4JVHJIvcH3AtnNGT6t sMnOUMqOkDn2kJpNDhy1zrUzS1X9bjoFKEINYlubfI0+cPt3ZZjvGcMKbV4Pyt4E g3Ib0M0TeixKfusdOHxc5SMkKE6vXHlxvDMW1kZI/Lv7Q7UbPzz5UqZguwZW04h2 AbI3yOI3yEIA1trrWtuvyJIhHXxxUatj/effwJCQIbVph8gzsJt0EcJtvofRMCZ8 ij6qE5MdPMHt16NZ48ugAeyiklC9eFjuan/oZa+Gi6wPlhbiwJuKwgT5pXdNw3kW z8+moTANtBnzfNc3uOLTrA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1722422373; x= 1722508773; bh=GHJ3FYAOhn+I0/+mFW/l1foRVbkKVNCSpEnXb9LzW8U=; b=f r9GrNzRIKn/3DnBXLqrrB+/8AqnefGS8TL8UkHtZIf2u6BSC5ov1SVbGjCIe0uBf GqNVwSick6jMf4aig3bUQ34vi0qkYARq5Ti+b8D64/DyE8rBqgMxhi/f4ySJVIMF moFUIVI6EJ4HGdPZeTpZ6lD8hYxTiagSoHw+iHmtfcMM6vNutW97wITy3M3kT9gT Z2hY6+zTMrUBK2Q81uuPyHG6IOsKWASHMhleCFxVRZMoQDE+EEsF0QiD97HjjEWM LhXRQRdftBR2d8JLB42+lVCdn5ZzQuChurA2rj5pNtq87D5Hs7g7KgMRJkVMe3w3 EQ0UW7KbqY0PEMdJFWmjQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrjeeigdefvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvfevufffkfgjfhgggfgtsehtqhertddttdejnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepffdtuefhhedvkeelleevffdvlefhleehvdegtddvvdduueeivedt gfejvddugeefnecuffhomhgrihhnpeguphgukhdrohhrghenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhn rdhnvghtpdhnsggprhgtphhtthhopedt X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 31 Jul 2024 06:39:31 -0400 (EDT) From: Thomas Monjalon To: Yaron Illouz Cc: "users@dpdk.org" , "dev@dpdk.org" , Konstantin Ananyev , Radu Nicolau , Akhil Goyal , Kai Ji , Anoob Joseph Subject: Re: ipsec on dpdk Date: Wed, 31 Jul 2024 12:39:30 +0200 Message-ID: <3105959.ktpJ11cQ8Q@thomas> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Hello, Adding Cc some experts. About the IPsec support, we are writing a document, it is in progress. 28/07/2024 14:51, Yaron Illouz: > Hi >=20 > I am interested to do ipsec encoding and decoding in my dpdk application > From my readings, i understand ipsec can be done one time in the nic (inl= ine ipsec) or with multiple calls (rte_cryptodev_enqueue_burst, rte_cryptod= ev_dequeue_burst....) >=20 >=20 > 1. If ipsec is done by nic I only need to call rte_ipsec_pkt_process(.= =2E.) without other functions? >=20 > I use rte_eth_rx_burst to read from nic. >=20 > 1. Where do I see list of nic that support nic inline ipsec? I believe= not all dpdk nic support it. > 2. How much does it impact performance ? is there a table of performan= ce per nic? > 3. My application is multi process, I can see in documentation : >=20 > =E2=80=9CCurrently, the security library does not support the case of mul= ti-process. It will be updated in the future releases.=E2=80=9D From https:= //doc.dpdk.org/guides/prog_guide/rte_security.html >=20 > So ipsec also is not supported for multi process application? >=20 > Even if done inline by the nic? >=20 > And what about non inline ipsec for multi process applications? >=20 >=20 >=20 > 1. Is ip sec also supported in multi queue with rte flow in the inline= ipsec ? >=20