From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: DPDK techboard minutes for 19th of December Date: Thu, 17 Jan 2019 09:49:24 -0800 Message-ID: <20190117094924.1fa8148b@hermes.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit To: dev@dpdk.org Return-path: Received: from mail-pf1-f174.google.com (mail-pf1-f174.google.com [209.85.210.174]) by dpdk.org (Postfix) with ESMTP id 69A182BF4 for ; Thu, 17 Jan 2019 18:49:33 +0100 (CET) Received: by mail-pf1-f174.google.com with SMTP id b85so5176509pfc.3 for ; Thu, 17 Jan 2019 09:49:33 -0800 (PST) Received: from hermes.lan (204-195-22-127.wavecable.com. [204.195.22.127]) by smtp.gmail.com with ESMTPSA id g2sm3071495pfi.95.2019.01.17.09.49.31 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 17 Jan 2019 09:49:32 -0800 (PST) List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Meeting notes for the DPDK technical board meeting held on 2019-12-19 Sorry for the belated minutes, but the puppy hair killed my desktop ;-) Attendees: 6/9 - Thomas Monjalon - Bruce Richardson - Ferruh Yigit - Maxime Coquelin - Olivier Matz - Stephen Hemminger KNI The existing KNI device is getting trimmed for 19.02. Consensus this is good, and hope is that KNI can get more work to improve performance (currently virtio is faster). Build System Still not enough automated build and testing is done on DPDK patches. Investigating getting Open Build Service (SUSE) as continuous build service to check all patches on all architectures. Luca will do more investigation. Mentoring Testing and build systems are a good way to get new people involved. Shemminger will look into applying for Google Summer of Code mentoring. Test Lab Discussion of current test lab. Current testing is limited to single core and only a performance test. Consensus that more investment and time is needed to get results from the lab. A wider scope is needed. What about testing stable branches as well? Process discussion Ongoing Discussion about gerrit etc. versus current process. Everyone agrees that current dev mailing list is overloaded to the point that only a few people read all of it. Ideas included splitting the mailing list along functional lines (crypto, compress, ipsec, ...) but concern that then overlapping patches would not get reviewed. General conclusion that mail is not scaling well, some alternative mail clients and tools discussed but no actions taken.