From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 0B79C8D95 for ; Mon, 30 Nov 2015 21:51:00 +0100 (CET) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga101.fm.intel.com with ESMTP; 30 Nov 2015 12:50:59 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,365,1444719600"; d="scan'208";a="610178485" Received: from irsmsx105.ger.corp.intel.com ([163.33.3.28]) by FMSMGA003.fm.intel.com with ESMTP; 30 Nov 2015 12:50:59 -0800 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.23]) by irsmsx105.ger.corp.intel.com ([169.254.7.203]) with mapi id 14.03.0248.002; Mon, 30 Nov 2015 20:50:58 +0000 From: "O'Driscoll, Tim" To: "dev@dpdk.org" Thread-Topic: 2.3 Roadmap Thread-Index: AdErsIjfg5kVwCCOTr635FzIeMmmbw== Date: Mon, 30 Nov 2015 20:50:58 +0000 Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA674705F1@IRSMSX108.ger.corp.intel.com> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-inteldataclassification: CTP_IC x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsIiwiaWQiOiJiZDExZjUxYS00NWU4LTQ0NjMtYjBhMS0yNzUwYjhmN2NmZjAiLCJwcm9wcyI6W3sibiI6IkludGVsRGF0YUNsYXNzaWZpY2F0aW9uIiwidmFscyI6W3sidmFsdWUiOiJDVFBfSUMifV19XX0sIlN1YmplY3RMYWJlbHMiOltdLCJUTUNWZXJzaW9uIjoiMTUuNC4xMC4xOSIsIlRydXN0ZWRMYWJlbEhhc2giOiJqWkFYanVGWHZtbDh1aXJUbERJUnljVDRpT25YQ0JocHZaVys1ZlkxZEtNPSJ9 x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [dpdk-dev] 2.3 Roadmap X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Nov 2015 20:51:01 -0000 As we're nearing the completion of the 2.2 release, I'd like to start a dis= cussion on plans for 2.3. To kick this off, below are the features that we'= re hoping to submit for this release. If others are prepared to contribute their plans, then we could build a com= plete view of the release which Thomas can maintain on the dpdk.org roadmap= page, and make sure we're not duplicating work. IPsec Sample Application: A sample application will be created which will s= how how DPDK and the new cryptodev API can be used to implement IPsec. Use = of the cryptodev API will allow either hardware or software encryption to b= e used. IKE will not be implemented so the SA/SP DBs will be statically con= figured. Cryptodev Support for SNOW 3G: The cryptodev API, and the hardware and soft= ware crypto PMDs that it supports, will be enhanced to support the SNOW 3G = cipher. External Mempool Manager: SoCs and some software applications that use DPDK= have their own memory allocation capabilities. This feature will allow DPD= K to work with an external mempool manager. Packet Framework (Edge Router Use Case): - Further performance tuning for the vPE use case. - Support for load balancing within a pipeline. - Support for CPU utilization measurements within a pipeline. - Improvements for the functional pipelines, tables and ports. Ethdev Enhancements: Merge parts of the Packet Framework ports library into= ethdev so they can be used without the Packet Framework. The initial focus= is to add support for buffered TX to ethdev. Live Migration: The main infrastructure to support live migration of VMs wa= s implemented over the last few DPDK releases via the Link Bonding and PCI = Hot Plug features. This feature will involve further investigation, prototy= ping and enhancements to improve live migration support in DPDK. Tcpdump Support: Support for tcpdump will be added to DPDK. This will impro= ve usability and debugging of DPDK applications. Increase Next Hops for LPM (IPv4): The number of next hops for IPv4 LPM is = currently limited to 256. This will be extended to allow a greater number o= f next hops. Fm10k Enhancements: FTAG based forwarding, and performance tuning Support Intel Resource Director Technology: A library will be added to DPDK= to support the following Intel CPU technologies: - CAT - Cache Allocation Technology (LLC aka L3) - CDP - Code Data Prioritization (extension of CAT) - CMT - Cache Monitoring Technology (LLC) - MBM - Memory Bandwidth Monitoring, to local and remote RAM These technologies are currently available via cgroups and perf, but this f= eature will provide closer integration with DPDK and a sample application s= howing how they can be used. I40e Enhancements: - Flow Director input set Alignment - Ethertype configuration for QinQ support - Flow Director Support for Tunnels (QinQ, GRE/NVGRE, VXLAN) - Flow Director Support for IP Proto and IP TOS - VEB switching - Floating VEB - IPGRE Support - Set VF MAC address - Rework PCIe extended tag enabling by using DPDK interfaces Virtio/Vhost Enhancements: - Virtio 1.0 support - Vhost software TSO - Vhost/virtio performance tuning Container Enhancements: - Virtio for containers - Hugetlbfs mount point size - Cgroup resource awareness=20 - Enable short-lived DPDK applications Generic Tunneling API: - Implement virtual flow device framework - Implement generic virtual device management APIs, including the following= callback functions: - flow_ethdev_start/stop/configure/close/info_get - ethdev_rx/tx_queue_setup/release - flow_ethdev_tunnel_configure/setup/destroy - flow_ethdev_tunnel_pkt_decap/encap - Implement flow device PMD drive APIs - rte_eth_flow_dev_create/remove/ others - Integrate VXLAN protocol (including VXLAN decap/encap optimization) into = this framework only on i40e. Tim