From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas@monjalon.net>
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com
 [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 725431B210
 for <users@dpdk.org>; Mon,  6 Nov 2017 02:02:53 +0100 (CET)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
 by mailout.nyi.internal (Postfix) with ESMTP id 5BCB620A8B;
 Sun,  5 Nov 2017 20:02:51 -0500 (EST)
Received: from frontend2 ([10.202.2.161])
 by compute1.internal (MEProxy); Sun, 05 Nov 2017 20:02:51 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h=
 cc:content-transfer-encoding:content-type:date:from:in-reply-to
 :message-id:mime-version:references:subject:to:x-me-sender
 :x-me-sender:x-sasl-enc; s=mesmtp; bh=+GgvNNPKt5aF/zlAKA6Gf0PMbR
 eke7bKXxdpV4wwiqE=; b=ho176hUmbvFIXVWiwhJ1goOxlEtxuvvtO5eCfMkCxI
 vfFGvvitGgLjztr+MNkZqiAnzfGZ+tRVM4TBchXgONYMHHTVHLh5E48N7vk5prsP
 mJIuTAlB3o3KwhcIRI2vBMcqXpffSRAQmX6i5Y/1DOLU3Kf5zHFgbXhYfNU/+q64
 g=
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-sender:x-me-sender:x-sasl-enc; s=fm1; bh=+GgvNN
 PKt5aF/zlAKA6Gf0PMbReke7bKXxdpV4wwiqE=; b=kz8XsPCry8DI63T1z0BIZm
 v2ECPaMLXfIgtqWLwCZcwX0DAsevBKTC8SIy8fPphXKHxeBzR2+r7AQHDqvysybG
 +Jes6RGbdp1Oopbk4TJiedrl8AyRrrEn41xVsMDKzT5YJfEK5+lyYvn5Le/ASHNS
 Yjbn3Y7jTcK8JTiJfkbFpNXzxxiZMSb6XMr4PXTTrUhmUO8iBrMsV03wweSLE+GK
 C2UlR0guxNwBATq492JyMqYMbVSHYcnhE8UOLl+wLA+GmfTXmaQY7WIpvDsM1PWT
 Qe9uhaxscRIhj59LZUMdJpI1sHmagQEACgDhs9SZ/0Sw/dFcrbzSSCgOz9cAj9Yg
 ==
X-ME-Sender: <xms:u7T_Wc_SHDruaTDFN5-nmIN2uoA_jO46_LTDNXv140iuhI2FJhKzxg>
Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184])
 by mail.messagingengine.com (Postfix) with ESMTPA id 1B993240B2;
 Sun,  5 Nov 2017 20:02:51 -0500 (EST)
From: Thomas Monjalon <thomas@monjalon.net>
To: "Avi Cohen (A)" <avi.cohen@huawei.com>
Cc: users@dpdk.org
Date: Mon, 06 Nov 2017 02:02:50 +0100
Message-ID: <4048707.fcLJULAWd5@xps>
In-Reply-To: <B84047ECBD981D4B93EAE5A6245AA361013EFADB@FRAEML521-MBX.china.huawei.com>
References: <B84047ECBD981D4B93EAE5A6245AA361013EFADB@FRAEML521-MBX.china.huawei.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [dpdk-users] IPsec offload
X-BeenThere: users@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK usage discussions <users.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/users>,
 <mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/users>,
 <mailto:users-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2017 01:02:53 -0000

Hi,

05/11/2017 09:32, Avi Cohen (A):
> Does the DPDK  support HW IPsec offload ?
> can DPDK configure the NIC/Network adapter to ipsec a specific flow ?

Yes, an experimental IPsec offload support is added in DPDK 17.11.
It is called rte_security:
	http://dpdk.org/doc/guides/prog_guide/rte_security.html

The hardware support will probably be improved in DPDK 18.02.