From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: dpdk-techboard <techboard@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Minutes of Technical Board Meeting, 2023-September-20
Date: Thu, 21 Sep 2023 10:43:07 +0200 [thread overview]
Message-ID: <71e464a7-4eee-9aa5-a1c8-29afa0733556@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2323 bytes --]
# Techboard attendees
- Bruce Richardson
- Hemant Agrawal
- Honnappa Nagarahalli
- Jerin Jacob
- Kevin Traynor
- Konstantin Ananyev
- Maxime Coquelin (Chair)
- Stephen Hemminger
- Thomas Monjalon
# General information
- Next meeting will take place on October 4th, and will be chaired by
Stephen Hemminger.
# Agenda
- Event dispatcher library inclusion
- Memarea library inclusion (Submitter not attending)
- Process to add new drivers
- Bugzilla maintenance: request for volunteers
- Power management brainstorming
# Minutes
## Event dispatcher library inclusion
- Mattias Rönnblom from Ericsson presented the Event dispatcher library
aims and implementation to the board, see attached slide set.
- The library was initially proposed as part of the Eventdev library as
a RFC in 2021. It has been moved to a dedicated library because it could
support other source than Eventdev.
- The goal is to decouple application modules in event-based applications.
- Modules register events to the dispatcher by providing match function,
callback and associated data.
- The library, which is about 1.2KLoC, also comes with documentation
(API, programming guide) and a test suite.
- Some possible future developments are discussed, including possibility
of HW offload to help the dispatching. Future developments will be
discussed on the mailing list.
- The technical board voted for the inclusion of this new library in
DPDK repository.
## Memarea library inclusion
- Topic not covered because the library author was not present.
## Process to add new drivers
- During the review of the Napatech ntnic driver, some discussions arose
about the driver inclusion process.
- The process for driver inclusion is more relaxed than the one for
libraries, but maintainers have some expectations on how the patch
series should be split.
- Even if it can sometimes look like a difficult task, the general idea
is to have a split per feature in order to make the review process easier.
- For the Napatech driver specifically, the author agreed to rework the
series to follow this guideline. Ferruh will share examples of other
drivers submissions doing that.
## Bugzilla maintenance: request for volunteers
- Topic not covered due to lack of time.
## Power management brainstorming
- Topic not covered due to lack of time.
[-- Attachment #2: DPDK Dispatcher Library PA1.pdf --]
[-- Type: application/pdf, Size: 573731 bytes --]
reply other threads:[~2023-09-21 8:45 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=71e464a7-4eee-9aa5-a1c8-29afa0733556@redhat.com \
--to=maxime.coquelin@redhat.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).