DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>,
	Harry van Haaren <harry.van.haaren@intel.com>,
	"techboard@dpdk.org" <techboard@dpdk.org>
Subject: Minutes of Technical Board Meeting, 2022-02-09
Date: Mon, 14 Feb 2022 13:46:03 +0000	[thread overview]
Message-ID: <a91263a0-0404-9ca1-5a8b-eff431260a6c@intel.com> (raw)

Tech Board Attendees:
     Aaron, Bruce, Ferruh (Chair), Hemant, Honnappa, Jerin, Kevin, Konstantin, Maxime, Olivier, Stephen, Thomas

Agenda Items
--------------
* Userspace event
   * Venue and date discussion is going on with e-mail, will be decided there.
  
* Traffic generator
   * Approved to have it in DPDK, scope will be documented to clear expectations
   * Implementation details will be discussed in ML, but initially it may have library and an application
     * Core libraries shouldn't depend on this library, library can be disabled
     * Library and application shouldn't enforce new external dependency

* Python binding for CI
   * Requested to help DTS, it is big task just for testing
   * Instead can develop C application to be used by DTS
   * Or testpmd can be improved, and perhaps a new interface can be created for DTS, to fill the feature gap

* UNH Statement of Work
    * About to be finalized, going to governing board for approval.
    * Techboard will comment on prioritization, Aaron will start an email thread for it.


Next meeting will be on 23 February, and Hemant will chair it.

                 reply	other threads:[~2022-02-14 13:46 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=a91263a0-0404-9ca1-5a8b-eff431260a6c@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=harry.van.haaren@intel.com \
    --cc=hemant.agrawal@nxp.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).