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 1A46F1B395
 for <users@dpdk.org>; Wed,  8 Nov 2017 13:39:47 +0100 (CET)
Received: from 172.18.7.190 (EHLO LHREML711-CAH.china.huawei.com)
 ([172.18.7.190])
 by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued)
 with ESMTP id DZK20277; Wed, 08 Nov 2017 12:39:46 +0000 (GMT)
Received: from FRAEML702-CAH.china.huawei.com (10.206.14.33) by
 LHREML711-CAH.china.huawei.com (10.201.108.34) with Microsoft SMTP Server
 (TLS) id 14.3.361.1; Wed, 8 Nov 2017 12:39:46 +0000
Received: from FRAEML521-MBX.china.huawei.com ([169.254.1.209]) by
 fraeml702-cah.china.huawei.com ([10.206.14.33]) with mapi id 14.03.0361.001;
 Wed, 8 Nov 2017 13:39:42 +0100
From: "Avi Cohen (A)" <avi.cohen@huawei.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>, 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/8wbdwgAZ134D//+2wEA==
Date: Wed, 8 Nov 2017 12:39:42 +0000
Message-ID: <B84047ECBD981D4B93EAE5A6245AA361013F129F@FRAEML521-MBX.china.huawei.com>
References: <B84047ECBD981D4B93EAE5A6245AA361013EFADB@FRAEML521-MBX.china.huawei.com>
 <4048707.fcLJULAWd5@xps>
 <B84047ECBD981D4B93EAE5A6245AA361013EFB60@FRAEML521-MBX.china.huawei.com>
 <7246948.uKqDaxhOvY@xps>
 <B84047ECBD981D4B93EAE5A6245AA361013F1260@FRAEML521-MBX.china.huawei.com>
 <E115CCD9D858EF4F90C690B0DCB4D8976CC46989@IRSMSX108.ger.corp.intel.com>
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8976CC46989@IRSMSX108.ger.corp.intel.com>
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.0A020202.5A02FB13.0051, 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: a375d8f16170297ab738195d38eb714e
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: Wed, 08 Nov 2017 12:39:48 -0000

>=20
> Even though Thomas is the DPDK main tree maintainer and that has a vast
> knowledge of it :), Don't expect him to know about what an Intel NIC supp=
orts.
>=20
> You are looking at two different things here. QAT driver works on the QAT
> devices mentioned above.
> But you are looking for inline crypto capability in NIC devices, there is=
 no
> reference in our documentation yet.
> We will add that shortly.
>=20
[Avi Cohen (A)]=20
Thank you Pablo
How can I be notified when updated ?
Regards,
Avi=20