From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: dev@dpdk.org
Subject: Re: DPDK User Space: Session onUseability and Ease of Use
Date: Tue, 13 Oct 2015 22:06:16 +0200 [thread overview]
Message-ID: <20640153.utfZ9qTjoW@xps13> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE202380B58@IRSMSX103.ger.corp.intel.com>
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
next prev parent reply other threads:[~2015-10-13 20:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 18:29 DPDK User Space: Session onUseability and Ease of Use Thomas F Herbert
2015-10-13 16:36 ` Mcnamara, John
2015-10-13 20:06 ` Thomas Monjalon [this message]
2015-10-14 6:51 ` Dave Neary
2015-10-14 13:16 ` Vincent JARDIN
2015-10-14 10:25 ` Panu Matilainen
2015-10-14 13:21 ` Vincent JARDIN
2015-10-14 14:36 ` Vincent JARDIN
2015-10-14 16:34 ` Bruce Richardson
2015-10-19 13:55 ` Simon Kågström
-- strict thread matches above, loose matches on Subject: below --
2015-10-08 16:38 Thomas Herbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20640153.utfZ9qTjoW@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.