From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <avi.cohen@huawei.com>
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17])
 by dpdk.org (Postfix) with ESMTP id 42BD71B300
 for <users@dpdk.org>; Mon,  6 Nov 2017 16:53:27 +0100 (CET)
Received: from 172.18.7.190 (EHLO LHREML711-CAH.china.huawei.com)
 ([172.18.7.190])
 by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued)
 with ESMTP id DSC62318; Mon, 06 Nov 2017 15:53:25 +0000 (GMT)
Received: from FRAEML701-CAH.china.huawei.com (10.206.14.32) by
 LHREML711-CAH.china.huawei.com (10.201.108.34) with Microsoft SMTP Server
 (TLS) id 14.3.361.1; Mon, 6 Nov 2017 15:53:24 +0000
Received: from FRAEML521-MBX.china.huawei.com ([169.254.1.209]) by
 FRAEML701-CAH.china.huawei.com ([10.206.14.32]) with mapi id 14.03.0361.001;
 Mon, 6 Nov 2017 16:53:18 +0100
From: "Avi Cohen (A)" <avi.cohen@huawei.com>
To: Thomas Monjalon <thomas@monjalon.net>
CC: "users@dpdk.org" <users@dpdk.org>, "olgas@mellanox.com"
 <olgas@mellanox.com>
Thread-Topic: [dpdk-users] IPsec offload
Thread-Index: AdNWEJZww10MSYRtTmqj3ER7vsBW+wAgf84AABWgwGD///12AP//of+g
Date: Mon, 6 Nov 2017 15:53:16 +0000
Message-ID: <B84047ECBD981D4B93EAE5A6245AA361013F0FF1@FRAEML521-MBX.china.huawei.com>
References: <B84047ECBD981D4B93EAE5A6245AA361013EFADB@FRAEML521-MBX.china.huawei.com>
 <4048707.fcLJULAWd5@xps>
 <B84047ECBD981D4B93EAE5A6245AA361013EFB60@FRAEML521-MBX.china.huawei.com>
 <7246948.uKqDaxhOvY@xps>
In-Reply-To: <7246948.uKqDaxhOvY@xps>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.202.145]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0),
 refid=str=0001.0A020206.5A008575.010B, ss=1, re=0.000, recu=0.000, reip=0.000,
 cl=1, cld=1, fgs=0, ip=169.254.1.209,
 so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 49c02e895fcedd6271fad424c17d48d4
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 15:53:27 -0000

Thank you Thomas
When I run the ipsec-secgw sample app. The program is exiting  with error '=
Mandatory option "-f" not present'=20
What is this option ? config file ?=20
Regards
Avi

> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Monday, 06 November, 2017 1:13 PM
> To: Avi Cohen (A)
> Cc: users@dpdk.org; olgas@mellanox.com
> Subject: Re: [dpdk-users] IPsec offload
>=20
> 06/11/2017 11:25, Avi Cohen (A):
> > Thank you Thomas
> > Is this was tested on a specific HW e.g.  Mellanox Innova  / other ?
>=20
> Mellanox hardware will probably be supported in 18.02.
> There are some experimental support for NXP DPAA2 and Intel ixgbe in DPDK
> 17.11.
>=20
>=20
> > > -----Original Message-----
> > > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > >
> > > 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.
>=20
>=20