From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id 50A1EDE3 for ; Thu, 24 May 2018 18:30:02 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 May 2018 09:29:59 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,436,1520924400"; d="scan'208,217";a="49829686" Received: from irsmsx153.ger.corp.intel.com ([163.33.192.75]) by fmsmga002.fm.intel.com with ESMTP; 24 May 2018 09:29:59 -0700 Received: from irsmsx156.ger.corp.intel.com (10.108.20.68) by IRSMSX153.ger.corp.intel.com (163.33.192.75) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 24 May 2018 17:29:58 +0100 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.179]) by IRSMSX156.ger.corp.intel.com ([169.254.3.233]) with mapi id 14.03.0319.002; Thu, 24 May 2018 17:29:58 +0100 From: "Mcnamara, John" To: "dev@dpdk.org" Thread-Topic: DPDK Release Status Meeting 24/05/2018 Thread-Index: AdPzfGDQm4vZSduESa6Hxg2BLtOE1g== Date: Thu, 24 May 2018 16:29:57 +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: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZDY5YWM3ZTAtMDAxZC00ZmYyLWJkMTYtMjIxN2ZkNjQ2YTVkIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiVjAzd2czZmpScXNkQk0wdzZqdjl3ZDJ3T0FVV1pVVVhJbTB5d1RlM0t1MHk5bWFvUFY0TW9JNk1rMTRwQURIWCJ9 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 24/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: Thu, 24 May 2018 16:30:04 -0000 The DPDK Release Status Meeting is mainly intended for DPDK Committers to discuss the status of the master and sub-trees. It is also intended as an update for project managers who need 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. Minutes 24 May 2018 Agenda * RC5 Status * RC6 and Release * Other items Participants: * Intel * Cavium * Mellanox * NXP * 6Wind * RedHat RC5 Status * Testing * Intel Testing * No major issues * No build issues * NXP * Good * Cavium * 1 issue found in bonding testing - patch submitted * RC5 Main Issues * Note, the following 2 issues will be included in the release. The will be marked as known issues in the release notes. * Bugzilla #50 - Secondary process launch is unreliable. https://dpdk.org/tracker/show_bug.cgi?id=3D50 Secondary process initialization was known to be unreliable befor= e, with numerous workarounds already being available and documented. However, DPDK version 18.05 has introduced memory subsystem rework, which has made situation worse due to much more memory being pre-reserved at initialization. * Bugzilla #48 -Unexpected performance regression since CVE-2018-10= 59 fix with vector path. https://dpdk.org/tracker/show_bug.cgi?id=3D48 A small performance drop was expected with CVE-2018-1059 fix integration. While this expectation is verified for mast cases (less than 3% drop), a bigger drop is seen when using vector path= in guest with small packets. RC6+ * Only critical fixes into RC6 * Docs also. Send deprecation notices. * Planned for Friday 25 May. End of day. * Automated test will run over weekend. * Results will be evaluated on Monday 28th May. * Depending on the results the release will be Monday or Tuesday 28th or 29th May. * All major contributors should evaluate on Monday and inform Thomas of your results: Intel, Cavium, Mellanox, NXP, 6Wind, RedHat, Debian, Canonical, etc. * Note: can all major contributors submit a "Tested Platforms" section to the release notes. Like this: http://dpdk.org/doc/guides/rel_notes/release_17_11.html#tested-platform= s Other * We will conduct a retrospective of 18.05 at next weeks meeting. Please think about: * What went well * What went badly * What we can do to improve