From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id E9059199B5 for ; Fri, 18 May 2018 18:47:25 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga007.jf.intel.com ([10.7.209.58]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 May 2018 09:47:24 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,415,1520924400"; d="scan'208,217";a="42067980" Received: from irsmsx101.ger.corp.intel.com ([163.33.3.153]) by orsmga007.jf.intel.com with ESMTP; 18 May 2018 09:47:23 -0700 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.179]) by IRSMSX101.ger.corp.intel.com ([169.254.1.118]) with mapi id 14.03.0319.002; Fri, 18 May 2018 17:47:22 +0100 From: "Mcnamara, John" To: "dev@dpdk.org" Thread-Topic: DPDK Release Status Meeting 17/05/2018 Thread-Index: AdPuxzWW5a6vljdBSKOmx7sRtV0Ktg== Date: Fri, 18 May 2018 16:47:21 +0000 Message-ID: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMmM2OTM4NWMtYTliNC00NjIxLTk5OGUtMDQxNWZiZmFhYjk3IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoicmU0MHpiY1RpU0RyZXhkSVV5a2hVeHMxUlwvclcxV1hIY05EU3M0elhpY2hidW1STVpDR2F3TFMyMFRPbllFc2kifQ== dlp-product: dlpe-windows dlp-version: 11.0.200.100 dlp-reaction: no-action x-originating-ip: [163.33.239.182] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] DPDK Release Status Meeting 17/05/2018 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: Fri, 18 May 2018 16:47:26 -0000 For the last 3 weeks we have had an 30min inter-company weekly sync on the release status of the current DPDK release. It is mainly intended for DPDK Committers to discuss the status of the mast= er and sub-trees. It is also intended as an update for project managers who ne= ed to track progress or milestone dates. The meeting occurs on Thursdays at 8:30 UTC. If you wish to attend just sen= d me and email and I will send you the invite. I will forward the minutes on = a weekly basis. Please note in particular: * The need for someone to manage the issues in Bugzilla * The request for "Tested Platforms" information. Minutes 17 May 2018 09:32 Agenda RC4 Status Validation RC5 Participants: Intel Cavium Mellanox NXP 6Wind RedHat Debian Canonical RC4 Status Status of the Subtrees * Crypto * About 4 patches remaining to be merged * Next-net * Will pull from virtio * Also will pull from vendor subtrees * Bug fix patches today on Intel sub-sub tree * Thomas will continue to merge subtrees until RC5 * Thomas asked if we can we pull from subtrees more frequently * Maintainers agreed * All STV to test fixes on latest main * Vhost * Only 1 remaining patch to be reviewed/merged * Can be merged soon * Eventdev * Nothing remaining to be merged * Pipeline * Nothing remaining to be merged Validation status for RC4 * Intel * No showstoppers after RC4 * Testing looking gook good * More stable * Mellanox * Tracking defects * Mainly PMD fixes * Cavium * Mainly driver fixes and testing * NXP * No major items * Note: can all validation teams submit a Tested Platforms section to the release notes. Like this: http://dpdk.org/doc/guides/rel_notes/release_17_11.html#tested-pla= tforms GCC8 * DPDK will now compile with GCC8 * However Lagopus (and other applications) don't compile against DPDK * Patches from Andy Green (24 patches) to address some/all of these issu= es * Let's review the patches one-by-one Issue with Clang build * Fix submitted Bugzilla * We need someone to manage the open defects on Bugzilla * Required task would be to check defects, set importance/priority, repo= rt to this meeting once a week. Vhost-user perf drop after CVE fixes. * Perf drop higher than expected. 8% in vector 1-2% in other path. * What should we do about this * Mainly in the vector path * Won't have time to fix in this release * Very specific use case * Will track in Bugzilla: https://dpdk.org/tracker/show_bug.cgi?id=3D48 * Will also document this as a known issue in the Release Notes RC5+ * RC5 targeted for Monday 21 May * RC6 for doc and critical fixes and deprecation notices * Release date May 25th. 2018!!