From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: techboard@dpdk.org
Subject: [dpdk-dev] Minutes of Techboard meeting 2020-03-11
Date: Wed, 18 Mar 2020 09:20:53 +0000 [thread overview]
Message-ID: <20200318092053.GA1491@bricha3-MOBL.ger.corp.intel.com> (raw)
Attendees: all tech-board members attended
DPDK Scope & rte_graph Proposal
--------------------------------
* As previously discussed at the last meeting rte_graph will be accepted into
DPDK, but the question of what repository it is to be put into was not agreed
* Concern was raised as to the amount of content in the DPDK repository,
specifically:
* non-hardware related functionality, i.e. pure software libs for
packet processing
* unused or abandoned code/libraries in DPDK
* Suggestion was made that perhaps some libraries, such as rte_graph and
others, should be split into a separate repo
* brings back the idea of the core vs non-core DPDK
* distro's want to be able to optionally not include some DPDK
libraries, and this may aid that
* key difficulty remains how to determine what remains in main
repo and what gets split out
* No consensus was reached on splitting out libraries from main repo
* Decision was made that, lacking that consensus, rte_graph should not be
blocked from merge to the main repo
* Consensus also reached that we should always endeavour to remove any dead
code from DPDK, be it unused examples, libraries or drivers.
Userspace Conference and Call for Papers
-----------------------------------------
* Only one DPDK event currently planned for this year:
* DPDK Userspace, Bordeaux, Sept 24-25
* Draft CfP was already circulated for discussion among technical board with
some discussion taking place via email
* Discussion was held on the format of the conference:
* Suggestion was to separate one day for user talks about how DPDK
was used by applications - both OSS and proprietary
* Other day (assuming 2 day conference) was to cover DPDK internals
and additions
* Agreement that time for an in-person technical board meeting should
be built into the agenda
* Thomas, on behalf of Techboard, will enquire whether event can be
stretched to more than two days, e.g. 2 1/2 to account for
additional user content
* Techboard is happy to take on the task of reviewing and
accepting/rejecting the proposals for the conference.
Other Business
---------------
* Reviews are requests on web page changes for the CI, replacing the
community lab page with a more general one on testing:
http://mails.dpdk.org/archives/web/2020-March/001346.html
reply other threads:[~2020-03-18 9:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200318092053.GA1491@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--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).