DPDK patches and discussions
 help / color / mirror / Atom feed
From: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>
Subject: Minutes of Technical Board meeting 07-February-2024
Date: Sun, 11 Feb 2024 19:07:45 +0000	[thread overview]
Message-ID: <59d49453-83dc-4fee-ad65-f126e94417ce@yandex.ru> (raw)
In-Reply-To: <4701850e-eb7c-47b8-a58d-c9d82bf9d125@yandex.ru>



Members Attending
-----------------
Aaron Conole
Bruce Richardson
Hemant Agrawal
Honappa Nagarahalli
Jerin Jacob
Kevin Traynor
Konstantin Ananyev (chair)
Maxime Coquelin
Morten Brorup
Stephen Hemminger
Thomas Monjalon

NOTE: The technical board meetings are on every second Wednesday at 3 pm
UTC.
Meetings are public, and DPDK community members are welcome to attend.
Agenda and minutes can be found at http://core.dpdk.org/techboard/minutes

Next meeting will be on Wednesday 2024-Feb-21 @ 3pm UTC, and will
be chaired by Maxime.

Agenda Items
============

1. March webinar: Hyperscaling on DPDK (Nathan)
-----------------------------------------------
DPDK marketing team organizing the first of four planned DPDK webinars 
for this year. The topic will be Hyperscaling on DPDK.
Tim O'Driscoll (Intel) is already on board.
Call for more SMEs/panelists
For those who interested, please contact Nathan Southern 
<nsouthern@linuxfoundation.org>.
Deadline 24/02/21.

2. Additional documentation around security support within DPDK (Nathan)
------------------------------------------------------------------------
Suggestion for TB members to start working on a skeleton document, which
is supposed to cover:
- what is the current status
- what is missing and what we want to cover
- next steps to achieve the goal
TB members to participate: TBD

3. QUIC support within DPDK (Thomas)
------------------------------------
Open discussion on:
QUIC becomes quite popular, majority of implementations are in userspace.
Should we introduce QUIC support within DPDK?
In general TB would welcome such add-on to the DPDK.
Preferred approach - a new library within DPDK, that will provide 
generic implementation and ability for the HW vendors to implement
various HW offloads in a transparent way.
What API should be provided: should it be something async, queue based, 
like io_uring?
Possible integration with DPDK graph framework.
Consider a top/down approach to ease interation with existing usages.
Next steps: add QUIC support into DPDK roadmap as a "Nice to have - 
Future" items.


4. RX/TX support for different types of device memory (Honappa)
---------------------------------------------------------------
Based on proposed TCP optimization for AI/ML use-case within Linux kernel:
https://lwn.net/Articles/937882/
https://netdevconf.info/0x17/sessions/talk/device-memory-tcp.html
How applicable it is for DPDK ecosystem?
What is already implemented within DPDK, what is missing?
Was noted that DPDK already provides similar ability for packet I/O:
https://developer.nvidia.com/blog/optimizing-inline-packet-processing-using-dpdk-and-gpudev-with-gpus/
Though number of HW vendors who support such feature is limited right now.
No further discussion on that subject.



           reply	other threads:[~2024-02-11 19:07 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <4701850e-eb7c-47b8-a58d-c9d82bf9d125@yandex.ru>]

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=59d49453-83dc-4fee-ad65-f126e94417ce@yandex.ru \
    --to=konstantin.v.ananyev@yandex.ru \
    --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).