From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id E84EA72FA for ; Sat, 28 Apr 2018 02:51:46 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 2B6162183A; Fri, 27 Apr 2018 20:51:46 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 27 Apr 2018 20:51:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= mesmtp; bh=lv05ZrDL8jN74EtB7sMq6LpCOsh3hMcr2L52MY6xQeQ=; b=LdfLU X0owBuG5fUc5HpGOoQVE7/diZarnYW2hLB6ub9xQgsKr8spEGW8evRofzzTuSOsO Kn9EsArCMWxRobOQDiIscFMiE2P7TTI7tTYCCa0AMbVs1SvKfo0xM3V6FmE5cFw8 bgmX65nveSaa17ccmQofabc3XBc2wcXvUHjHH8= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=lv05ZrDL8jN74EtB7sMq6LpCOsh3h Mcr2L52MY6xQeQ=; b=Cu9mRQk/OS9oFoKdyjUHRHms4zKxmDvsNJG/ota5IoLQG 78Zd4MOmguvx6AI1ldaSh1EBcAglv6yvyRNnaic3OgV/9lbryibzzSx8bKopPZdC zYWJjQngQOZEylgwUWOX4chTwWYeIYNcMbR/G+uyNCoMdaInrKghOCfXkjjkj6d8 3pxQozmCvaoqM/0XPRSKX/By12OE7lO8WDip5x4w4Ukegrx9BoIxY7sZpGcDobyg 9jeQ4U33JWUc2gFaA97qwf6FOwiw150CN98XkVdCk44SIS95hIbanMRyl80DsSeV j/iDHzQXKKWkh2KL6MyPlmf4hUrALKnlhSn465AKQ== X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id BBA14E5098 for ; Fri, 27 Apr 2018 20:51:45 -0400 (EDT) From: Thomas Monjalon To: announce@dpdk.org Date: Sat, 28 Apr 2018 02:51:44 +0200 Message-ID: <2302207.sZ50dMT8GX@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: [dpdk-announce] release candidate 18.05-rc1 X-BeenThere: announce@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Apr 2018 00:51:47 -0000 A new DPDK release candidate is ready for testing: https://dpdk.org/browse/dpdk/tag/?id=v18.05-rc1 1138 patches: more than 18.02-rc2 which was really huge! This is one of the explanations for the big delay in this release. The release notes so far: http://dpdk.org/doc/guides/rel_notes/release_18_05.html Some highlights of 18.05-rc1: - memory subsystem rework - mempool bucket driver - improved logging control - uevent support for hotplug - generic multi-process channel (IPC) - secondary process support in virtual devices - ethdev API for recommended Rx/Tx parameters - ethdev API for various tunnels offloads - ethdev API for interconnect/switch offloads - ethdev port representor - axgbe AMD driver - bnxt update for Broadcom NetXtreme-S (Stingray) - cxgbe VF driver for Chelsio T5/T6 - mlx5 striding RQ (multi packets buffer) - mlx5 tunnels offloads extended - sfc update for Solarflare XtremeScale X2xxx - ifcvf vDPA driver for accelerated virtio with Intel FPGA - vhost selective datapath - vhost interrupt mode - virtio-user server mode - virtio-crypto driver - bonding support of flow API - ccp AMD crypto driver - eventdev timer adapter - IP pipeline enhancements Some features are expected in 18.05-rc2: - proper runtime files directory - compressdev - eventdev crypto adapter - NXP devices blacklisting - DPAA2 QDMA raw driver - DPAA2 Command Interface raw driver - Intel FPGA bus - Hyper-V bus and NetVSC driver - TAP TSO - BPF - testpmd simulation of noisy host Some planned features are postponed to 18.08: - new devargs syntax - libedit integration - clean-up of panic calls Please be aware that there are some API changes in 18.05: http://dpdk.org/doc/guides/rel_notes/release_18_05.html#api-changes You are especially encouraged to look closely at: - ethdev/PMD interface update; - flow API update, which may effect applications and PMDs. As a consequence, PMD developpers must test in depth their offloads and flow API support. Given the number of features pending for RC2, we can expect the next release candidate in two weeks, the 11th of May (which is late). Usually we need two more weeks of bug fixing in RC3 and RC4, and few more days of validation before the release. It means the release will happen during the last days of May. The cycle for 18.08 may need to be shortened, and the release lighter. If we are good at validations, and we do not invent too many new bugs, we can try to speed up that (realistic) schedule. Please do your best at testing and fixing this fat release. When finding a new bug, please report it on bugzilla: http://dpdk.org/tracker/ Thank you everyone