From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>
Subject: [dpdk-dev] DPDK techboard minutes of June 3rd
Date: Tue, 9 Jun 2020 17:50:32 +0000 [thread overview]
Message-ID: <BYAPR11MB33011747ED699989A08DDB489A820@BYAPR11MB3301.namprd11.prod.outlook.com> (raw)
Meeting notes for the DPDK technical board meeting held on 2020-05-20
TB Attendees:
- Bruce Richardson
- Ferruh Yigit
- Hemant Agrawal
- Honnappa Nagarahalli
- Jerin Jacob
- Kevin Traynor
- Konstantin Ananyev
- Maxime Coquelin
- Olivier Matz
- Stephen Hemminger
- Thomas Monjalon
NOTE: The technical board meetings every second Wednesday on IRC channel
#dpdk-board, at 3pm UTC.
Meetings are public and DPDK community members are welcome to attend.
1) DPDK charter update/review discussion
AR for all TB members to review draft version of the charter and provide their comments by mail.
AT to Bruce (as GB representative) to summarize these comments and present to the GB.
2) options/rules for new TX mbuf offload flags/fields (static vs dynamic)
See email threads:
http://mails.dpdk.org/archives/dev/2020-May/168810.html
http://mails.dpdk.org/archives/dev/2020-June/169215.html
As a generic rule - the preference is to use dynamic flags/fields to add new content into rte_mbuf.
If submitter requests static space reservation - he/she can request TB for an exception.
Right now there is no exact criteria specified (possible considerations include:
how widely the feature is used, how much cycles are lost in case it is dynamic, how many bytes it occupies).
TB decision regarding this particular case (3 TX offload flags for packet marking) - use dynamic flag allocation.
3) DPDK packaging
Proposition to have some common packaging recipes ready to use and community supported.
It would help those not expert of DPDK packaging and it could be used with Suse OBS CI service.
In general positive, if there are resources to maintain it.
AR for Thomas to consult with LTS maintainers (Luca, Kevin),
final decision based on their input.
Next meeting will be on Wednesday 2020-06-17 @3pm UTC, and will be
chaired by Maxime Coquelin.
reply other threads:[~2020-06-09 17:50 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=BYAPR11MB33011747ED699989A08DDB489A820@BYAPR11MB3301.namprd11.prod.outlook.com \
--to=konstantin.ananyev@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).