From: "Wiles, Keith" <keith.wiles@intel.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "techboard@dpdk.org" <techboard@dpdk.org>
Subject: Re: [dpdk-dev] next technical board meeting, 2017-04-06
Date: Thu, 30 Mar 2017 14:25:12 +0000 [thread overview]
Message-ID: <B4F733F5-B012-49B0-AA7F-D9942A6954C8@intel.com> (raw)
In-Reply-To: <20170330094058.nh2nhk4ko6tsqedn@localhost.localdomain>
> On Mar 30, 2017, at 4:41 AM, Jerin Jacob <jerin.jacob@caviumnetworks.com> wrote:
>
> Hello everyone,
>
> A meeting of the DPDK technical board will occur next Thursday,
> April 6th 2017 at 9am UTC?
>
> The meeting takes place on the #dpdk-board channel on IRC.
> This meeting is public, so anybody can join, see below for the agenda.
>
> Jerin
>
> 1) Divergence between DPDK/Linux PF/VF implementations.
>
> Discussions:
> http://dpdk.org/ml/archives/dev/2017-March/060529.html
> http://dpdk.org/ml/archives/dev/2017-March/060063.html
> http://dpdk.org/ml/archives/dev/2016-December/053056.html
>
> 2) Representative for the DPDK governance board
>
> 3) Scope of cmdline and cfgfile libraries in DPDK.
> Discuss the scope of cmdline and cfgfile libraries in DPDK
> and see if we allow more libs like that (Keith proposed a CLI lib),
> or we do not do more,
> or do we target to replace them by better external equivalents?
I would prefer not lumping cfgfile into the CLI discussion, we can have a different discussion on it later.
A couple of options for CLI are:
1 - Include CLI in DPDK repo, then start converting apps to CLI.
Keep or deprecate cmdline in the future.
2 - Include CLI in DPDK repo, do not convert current APPs allow new apps to use cmdline or CLI.
3 - Put CLI in a different repo in DPDK, do not convert apps to use CLI allow developers to decide if they want to use CLI.
- I would like to be able to clone CLI into DPDK lib directory and build it as a DPDK library.
This would mean updating common_base, lib/Makefile and rte.apps.mk using a patch or use common_base config option.
Building CLI outside of DPDK as a external lib is not very easy for developers to manage.
Could use a patch to include CLI into the DPDK build system, but just adding the configuration defaulted off is the cleaner way.
We talked about creating a new repo on DPDK.org and I am happy with it, just want it better integrated into DPDK as a first class library to make using it simpler and easier for developers.
Doing option #1 or #2 is my first choice, but option #3 is good if we can have it as a first class library.
>
> 4) Community questions/issues
>
>
>
Regards,
Keith
next prev parent reply other threads:[~2017-03-30 14:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 9:41 Jerin Jacob
2017-03-30 14:25 ` Wiles, Keith [this message]
2017-03-30 15:05 ` Olivier Matz
2017-03-30 15:51 ` Wiles, Keith
2017-03-30 16:03 ` Jay Rolette
2017-03-30 18:09 ` Dumitrescu, Cristian
2017-04-03 19:51 ` Stephen Hemminger
2017-04-03 22:53 ` Wiles, Keith
2017-04-04 1:28 ` Stephen Hemminger
2017-04-04 5:01 ` Vincent Jardin
2017-04-04 14:35 ` Wiles, Keith
2017-03-31 8:52 ` Olivier Matz
2017-03-31 9:31 ` Dumitrescu, Cristian
2017-03-31 14:24 ` Wiles, Keith
2017-03-31 14:39 ` Wiles, Keith
2017-04-06 10:01 ` Jerin Jacob
2017-04-10 6:49 ` [dpdk-dev] next technical board meeting, 2017-04-10 Yuanhan Liu
2017-04-10 14:34 ` Wiles, Keith
2017-04-10 14:43 ` Dumitrescu, Cristian
2017-04-10 14:54 ` Wiles, Keith
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=B4F733F5-B012-49B0-AA7F-D9942A6954C8@intel.com \
--to=keith.wiles@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=techboard@dpdk.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).