DPDK patches and discussions
 help / color / mirror / Atom feed
From: Olivier Matz <olivier.matz@6wind.com>
To: dev@dpdk.org
Subject: [dpdk-dev] DPDK techboard minutes 2018-07-04
Date: Mon, 16 Jul 2018 13:00:34 +0200	[thread overview]
Message-ID: <20180716110034.7p4cd6sc3omforcm@platinum> (raw)

Hi,

Here are the minutes of the last DPDK technical board meeting held on
2018-07-04.

Attendees: 6 / 8
- Bruce Richardson
- Ferruh Yigit
- Hemant Agrawal
- Jerin Jacob
- Olivier Matz
- Thomas Monjalon

1) minimal kernel version supported for DPDK

   - discussion should happen on ML first
   - decision is postponed to next techboard meeting

2) backport policy for fixes

   The technical board reviewed and approbed Kevin's clarified guideline:
   https://patches.dpdk.org/patch/42011/

3) "contribute" page on core.dpdk.org

   - We think that duplicating information between
     https://www.dpdk.org/contribute and http://core.dpdk.org/contribute/ is not
     a good thing.
   - Bruce to ask to LF to remove the git:// link and only keep the http://
     on https://www.dpdk.org/contribute
   - Thomas will send a proposal for the contribute page
   - Same comments about https://www.dpdk.org/ecosystem/#hardware vs
     https://core.dpdk.org/supported/
     The main website should stay general and applies to all dpdk projects.
   - We agreed that the ecosystem page (hardware + drivers) on the main website
     should only contain a list of brands (cpus + devices), plus a link to the
     core page that contains detailed information.

4) librte_rib library

   The new RIB library has been through a number of iterations. As a new
   library, it requires techboard discussion and approval before it can be
   accepted into DPDK.We also need to consider how to manage it vs existing LPM
   library. RIB lib looks overall better and faster but it lacks an IPv6 version
   compared to LPM.

   - The first step is to review it and make it in
   - As a next step, we should either remove lpm(v4) or do a shim so that lpm-v4
     uses librte_rib.
   - Olivier to help to review the library

5) SPDX licenses

   - Bruce and Ferruh to check if Intel shared code can have proper SPDX tags


Next Meeting:
- 2018-07-18
- Stephen to chair discussion

                 reply	other threads:[~2018-07-16 11:00 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=20180716110034.7p4cd6sc3omforcm@platinum \
    --to=olivier.matz@6wind.com \
    --cc=dev@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).