From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: DPDK User Space: Session onUseability and Ease of Use Date: Tue, 13 Oct 2015 22:06:16 +0200 Message-ID: <20640153.utfZ9qTjoW@xps13> References: <5616B611.3070900@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: "Mcnamara, John" Return-path: Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com [209.85.212.171]) by dpdk.org (Postfix) with ESMTP id A753A8D95 for ; Tue, 13 Oct 2015 22:07:21 +0200 (CEST) Received: by wijq8 with SMTP id q8so48917795wij.0 for ; Tue, 13 Oct 2015 13:07:20 -0700 (PDT) In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Thanks John for the summary. 2015-10-13 16:36, Mcnamara, John: > - Move the EAL to the kernel. Please explain what you mean here. It's difficult to imagine. > * Latest version of the docs. - Needs support from 6Wind. OK It's as simple as a git hook. Anybody to write and test one locally? The script could be hosted in the future website git repo. > * Distributed testing. - Needs support from Intel initially. > Some of this is already being rolled out on the > test-report@dpdk.org list for Intel hardware: > http://dpdk.org/ml/archives/test-report/. Other hardware > vendors could use the same automated test framework to host > something similar. IBM has first started a daily compilation test. Others are welcome. We had a small session dedicated to this topic during the useability session. > * Create a User Mailing List. - Needs support from 6Wind. OK Name: user@dpdk.org or other suggestion? > * Make the dpdk.org website patchable. - Needs support from > 6Wind. OK Needs a maintainer, a name for the git repo, the mailing list and the patchwork. > * Add a Contributing Guide. - I will submit a doc patch. > > * Add a README .txt or .1st to the root dir. - I will submit a > doc patch. Thanks > * Too much duplicated code in the PMDs. - Any volunteers to > refactor common PMD code up into the ethdev layer? We need more details. Please start a new thread or a RFC. > * Logging and debugging via a secondary process. Any volunteers > to add a sample app that demonstrates the technique? There is already one: http://dpdk.org/browse/dpdk/tree/app/proc_info/main.c#n289