DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>
Subject: [dpdk-dev] Minutes of Technical Board Meeting, 2020-11-18
Date: Sun, 22 Nov 2020 13:40:10 +0000	[thread overview]
Message-ID: <DM6PR11MB330899BE2BE4A963890FBC989AFD0@DM6PR11MB3308.namprd11.prod.outlook.com> (raw)

Minutes of Technical Board Meeting, 2020-11-18

Members Attending
-Konstantin (Chair)

NOTE: The technical board meetings every second Wednesday in
https://meet.jit.si/DPDK at 3 pm UTC.
Meetings are public, and DPDK community members  are welcome to attend.
NOTE: Next meeting will be on Wednesday 2020-12-02 @3pm UTC, and will be
chaired by Maxime.

DPDK build configuration - future enhancements
There are multiple requests (sometimes controversial) for new abilities
to add into DPDK build system.  
In particular, request from few different teams:
  - add ability to enable/disable individual apps/libs
  - override some build settings for specific libs/drivers
As a first step to move forward - produce design doc of current build system.
Discuss further enhancements based on that doc.
While planning changes to the build system backward compatibility
with 20.11 should be considered.
AR to Bruce to create initial version of the DD.

Asia DPDK Event 
Thomas provided quick update.
Few moderators (speaking mandarin) would be required.

             reply	other threads:[~2020-11-22 13:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-22 13:40 Ananyev, Konstantin [this message]
2020-11-23  9:30 ` Morten Brørup
2020-11-23 10:00   ` [dpdk-dev] [dpdk-techboard] " Thomas Monjalon
2020-11-23 11:16     ` Morten Brørup

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DM6PR11MB330899BE2BE4A963890FBC989AFD0@DM6PR11MB3308.namprd11.prod.outlook.com \
    --to=konstantin.ananyev@intel.com \
    --cc=dev@dpdk.org \
    --cc=techboard@dpdk.org \


* 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).