DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: "techboard@dpdk.org" <techboard@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Minutes of Technical Board Meeting, 2023-Jun-28
Date: Mon, 18 Sep 2023 05:18:14 +0000	[thread overview]
Message-ID: <PAXPR04MB932830250BB7F7E93268B00789FBA@PAXPR04MB9328.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <PAXPR04MB932824B064C14CEAE1093E93891CA@PAXPR04MB9328.eurprd04.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]

Minutes of Technical Board Meeting, 2023-Jun-28

Members Attending
-----------------
-Aaron
-Hemant (Chair)
-Jerin
-Keven
-Konstantin
-Maxime
-Stephen
-Nathan
-Ben

NOTE: The technical board meetings every second Wednesday at https://meet.jit.si/DPDK at 3 pm UTC.
Meetings are public, and DPDK community members are welcome to attend.
The agenda is available at: https://annuel.framapad.org/p/r.0c3cc4d1e011214183872a98f6b5c7db

NOTE: Next meeting will be on Wednesday 2023-July-12 @3pm UTC, and will be chaired by Honnappa



Newsletter
--------------
1. Ben reminded about the inputs for Newsletter. Expecting contributions.

Dublin DPDK submit
---------------------------

1) Decent amount of contribution received, the CFP date for 30th June may be extended.
2) 30 + Registrations

Other topics.
-------------------
1) Discussed about memarea library:
                - It is to provide a simple memory manager for non-huge page library
                - Stephen and Jerin will be providing feedback
2) Discussed the idea about pre-submitting code for 23.11 ABI compatibility.

[-- Attachment #2: Type: text/html, Size: 4337 bytes --]

           reply	other threads:[~2023-09-18  5:18 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <PAXPR04MB932824B064C14CEAE1093E93891CA@PAXPR04MB9328.eurprd04.prod.outlook.com>]

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=PAXPR04MB932830250BB7F7E93268B00789FBA@PAXPR04MB9328.eurprd04.prod.outlook.com \
    --to=hemant.agrawal@nxp.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).