From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by dpdk.org (Postfix) with ESMTP id A7D21567C for ; Sun, 15 Jan 2017 15:42:43 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5198; q=dns/txt; s=iport; t=1484491363; x=1485700963; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=QtGhjsfZF4NidCysjUubZT3Li4Dd7mC8sG1Q82eXo5s=; b=H13w9jqLsMLmiOlbWmnyC58eSy66ToEcdfIJWRIzIvTwE3EUqSmvyX/H rkvnf8LnODv8LimLXGOoZn0CwuiKFEbHMA85ebncE1MASzSCv80Wel6a0 k8F56Gbdyadv8ksVcUeqXboTCzpMF7EsVNpFr/L3qRNtTmKoyWze03BzK c=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AZAQAmiXtY/5BdJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgyoPAQEBAQEfX4EJB41RkhKVLIILLIJAgzYCghg/GAECAQEBAQE?= =?us-ascii?q?BAWMohGkBAQECAjo/DAQCAQgRBAEBHwkHMhQJCAEBBAENBQiIew6yEol8AQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBHYZFhGeCPIFpVYUyBZs6AYZcgxeHYoIAUY4liBq?= =?us-ascii?q?GP4QSAR84gUQVhGyCAHMBAYYkgS8BgQwBAQE?= X-IronPort-AV: E=Sophos;i="5.33,233,1477958400"; d="scan'208";a="193336021" Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 Jan 2017 14:42:41 +0000 Received: from XCH-RTP-018.cisco.com (xch-rtp-018.cisco.com [64.101.220.158]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id v0FEgfVY031880 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 15 Jan 2017 14:42:41 GMT Received: from xch-rtp-017.cisco.com (64.101.220.157) by XCH-RTP-018.cisco.com (64.101.220.158) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sun, 15 Jan 2017 09:42:41 -0500 Received: from xch-rtp-017.cisco.com ([64.101.220.157]) by XCH-RTP-017.cisco.com ([64.101.220.157]) with mapi id 15.00.1210.000; Sun, 15 Jan 2017 09:42:41 -0500 From: "Hanoch Haim (hhaim)" To: "O'Driscoll, Tim" , "dev@dpdk.org" CC: "Hanoch Haim (hhaim)" Thread-Topic: 17.05 Roadmap Thread-Index: AdJthHtgT93bnbBzSNmabkEXEAQoQwBuOokg Date: Sun, 15 Jan 2017 14:42:40 +0000 Message-ID: <051bd9fc38c14d04b214675123481be1@XCH-RTP-017.cisco.com> References: <26FA93C7ED1EAA44AB77D62FBE1D27BA722A7A17@IRSMSX108.ger.corp.intel.com> In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA722A7A17@IRSMSX108.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [64.103.125.60] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] 17.05 Roadmap X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jan 2017 14:42:44 -0000 Hi Tim,=20 It's great that you are going to expose the i40E Qos capability, would it b= e possible to expose the low-latency configuration too? Thanks, Hanoh -----Original Message----- From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of O'Driscoll, Tim Sent: Friday, January 13, 2017 12:24 PM To: dev@dpdk.org Subject: [dpdk-dev] 17.05 Roadmap Below are the features that we're planning to submit for the 17.05 release.= We'll submit a patch to update the roadmap page with this info. It would be good if others are also willing to share their plans so that we= can build up a complete picture of what's planned for 17.05 and make sure = there's no duplication. Cryptodev DES SW PMD: A PMD will be added which implements an optimized sof= tware version of the DES algorithm. Cryptodev DOCSIS BPI+: The cryptodev API will be enhanced to enable process= ing of packets according to the Baseline Privacy Interface Plus (BPI+) spec= ification described in the Data-over-Cable Service Interface Specification = (DOCSIS) Security Specification (http://www.cablelabs.com/wp-content/upload= s/specdocs/CM-SP-SECv3.1-I06-160602.pdf). See the RFC (http://dpdk.org/ml/a= rchives/dev/2016-December/052433.html) for further details. Support will be= added to the QAT PMD for AES and DES, to the new software PMD for DES (see= previous item), and to the existing AESNI_MB PMD. Cryptodev Scheduler: This allows packets to be encrypted/decrypted in eithe= r SW or HW depending on packet size and HW utilization. Reordering will be = supported so that packet order can be preserved. Ethernet 32-bit CRC Generation: An optimized x86 library for CRC-32 will be= added. A CRC may need to be generated for a downstream frame by the DOCSIS= MAC layer because the CRC may be removed by the NIC or the frame may be mo= dified by the MAC for PHS (packet header suppression).=20 API to Configure Programmable Devices: More devices are now supporting prog= rammable components, for example the Pipeline Personalization Profiles in I= 40E. An API will be added to allow any programmable device to be configured= . I40E Hardware QoS: Hardware QoS will be supported on the I40E. This will in= clude Tx bandwidth control (min and max), and Rx Traffic Class assignment. Configurable Tunnel Filters for I40E: DPDK support will be added for a new = I40E admin queue which allows configuration of filter types for cloud filte= rs. Enable MPLS on I40E: MPLSoUDP and MPLSoGRE will be supported for I40E, incl= uding the new protocols and filtering (RSS and Flow Director), checksum off= load and packet type recognition. Software Eventdev Implementation: The libeventdev API is being added in 17.= 02 (http://dpdk.org/ml/archives/dev/2016-December/052877.html). A software = implementation of this API will be added. New Vhost Device Type: The vhost-user framework will be expanded so that it= can support additional device types. Support for SCSI will be added initia= lly, but block devices and other device types may be added in future. Abstraction Layer for QoS: An abstraction layer for Quality of Service (QoS= ) hierarchical schedulers will be implemented. The goal of the abstraction = layer is to provide a simple generic API that is agnostic of the underlying= HW, SW or mixed HW-SW implementation. See the RFC (http://dpdk.org/ml/arch= ives/dev/2016-November/050956.html) for details. IPFIX Support: The Internet Protocol Flow Information Export (IPFIX) protoc= ol provides network administrators with access to IP Flow information. An o= bservation point (one for all the interfaces), metering process and an expo= rter process will be implemented. The observation point and metering proces= s will be as defined in RFC 5474 (https://tools.ietf.org/html/rfc5474). Interrupt Mode for Virtio-User: Interrupt mode support will be added for vi= rtio-user, which is a virtual device for high performance container network= ing. Automated VF Processing of PF Reset for I40E: In 16.07, changes were made f= or both IXGBE and I40E to notify a VF when a PF reset occurs. This will be = further enhanced for I40E so that the driver handles as much of the process= ing as possible, including things like resetting VF ports. Tx Buffering in Vhost PMD: Overall throughput drops as the number of guests= increases on a single host. This is because a Tx burst is spread across m= ultiple guests, so the burst size per guest decreases as the number of gues= ts increases. Tx buffering will be added which will increase the Tx burst s= ize and increase performance. Consistent PMD Batching Behaviour: PMD Tx batching behavior is not consiste= nt between PMDs. Some PMDs have no limit for nb_pkts (besides number of ava= ilable descriptors), some (like vhost) have a limit on the max number of Tx= packets (32 for vhost), and some define a max burst size and transmit pack= ets in multiple bursts up to that size. The application needs to manage the= se differences. To make things easier for application developers, we're con= sidering putting the logic for managing this directly into rte_eth_tx_burst= .