From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <helin.zhang@intel.com> Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 9BE9D37AF for <dev@dpdk.org>; Mon, 14 Sep 2015 10:41:18 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga103.jf.intel.com with ESMTP; 14 Sep 2015 01:41:17 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.17,526,1437462000"; d="scan'208";a="788915103" Received: from kmsmsx154.gar.corp.intel.com ([172.21.73.14]) by fmsmga001.fm.intel.com with ESMTP; 14 Sep 2015 01:41:16 -0700 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by KMSMSX154.gar.corp.intel.com (172.21.73.14) with Microsoft SMTP Server (TLS) id 14.3.224.2; Mon, 14 Sep 2015 16:40:22 +0800 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.210]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.12]) with mapi id 14.03.0248.002; Mon, 14 Sep 2015 16:40:21 +0800 From: "Zhang, Helin" <helin.zhang@intel.com> To: Thomas Monjalon <thomas.monjalon@6wind.com>, "O'Driscoll, Tim" <tim.o'driscoll@intel.com> Thread-Topic: [dpdk-dev] DPDK 2.2 roadmap Thread-Index: AQHQ68aWwDEKSn9ytEqvj1efiT1LA547qgug Date: Mon, 14 Sep 2015 08:40:20 +0000 Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A8FBC67@SHSMSX104.ccr.corp.intel.com> References: <1882381.9qlZTmz9zB@xps13> <26FA93C7ED1EAA44AB77D62FBE1D27BA67401646@IRSMSX108.ger.corp.intel.com> <2207263.dDyMmkz5Pr@xps13> In-Reply-To: <2207263.dDyMmkz5Pr@xps13> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" <dev@dpdk.org> Subject: Re: [dpdk-dev] DPDK 2.2 roadmap X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK <dev.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Mon, 14 Sep 2015 08:41:19 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon > Sent: Thursday, September 10, 2015 8:44 PM > To: O'Driscoll, Tim > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] DPDK 2.2 roadmap >=20 > 2015-09-09 12:56, O'Driscoll, Tim: > > DCB for i40e &X550: DCB support will be extended to the i40e and X550 = NICs. Yes, i40e DCB will be enabled in R2.2. >=20 > A patch for DCB on X550 is already applied but the release notes part was > forgotten. >=20 > > IPsec Sample App: A sample application will be provided to show how > > the cryptodev library can be used to implement IPsec. This will be > > based on the NetBSD IPsec implementation. >=20 > For each API, it is really interesting to have some unit tests and some e= xamples to > show how it should be used. However adding an IPsec stack looks to be bey= ond > the need of an API example. It may be big and difficult to maintain when > updating DPDK. > Why not spawn a new project here: http://dpdk.org/browse/ ? >=20 > > Refactor EAL for Non-PCI Devices: This has been discussed extensively = on the > mailing list. See the RFCs for Refactor eal driver registration code > (http://dpdk.org/ml/archives/dev/2015-September/023257.html) and Remove > pci driver from vdevs > (http://dpdk.org/ml/archives/dev/2015-August/023016.html). >=20 > I have the feeling we should think it as an unification work to reduce di= fferences > between physical and virtual devices handling. > Probably it will have to be continued during 2.3 cycle. >=20 > > Vhost Multi-Queue Support: The vhost-user library will be updated to p= rovide > multi-queue support in the host similar to the RSS model so that guest dr= iver may > allocate multiple rx/tx queues which then may be used to load balance bet= ween > cores. See http://dpdk.org/ml/archives/dev/2015-August/022758.html for mo= re > details. >=20 > Does it require a patch on Qemu? >=20 > > Config Granularity of RSS for i40e: All RSS hash and filter configurat= ions for > IPv4/v6, TCP/UDP, GRE, etc will be implemented for i40e. This includes su= pport > for QinQ and tunneled packets. >=20 > What is missing in i40e RSS/filtering? The fields used for HASH-ing is configured by firmware, some of users want = to have a bit more flexibility on selecting packet fields for hashing. >=20 > > I40e 32-bit GRE Keys: Both 24 and 32 bit keys for GRE will be supporte= d for > i40e. >=20 > Could you please give more details? Currently only 24 bits of GRE key will be used for hash/filter calculation,= while 32 bits was wanted by some of users. So either 24 or 32 bits can be selected by the= users from R2.2. >=20 > > X550 Enhancements: Support VF TSO, more Entries in RSS and per VF RSS, > network overlay support with flow director for X550. >=20 > Could you please give more details on "network overlay support with flow > director"? X550 hardware supports flow director on tunneled packets (VXLAN/NVGRE), the= se will be enabled from R2.2. Regards, Helin >=20 > Thanks for sharing your plan