From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 7062343AF0; Sun, 11 Feb 2024 20:07:51 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id EBBBB4026B; Sun, 11 Feb 2024 20:07:50 +0100 (CET) Received: from forward501b.mail.yandex.net (forward501b.mail.yandex.net [178.154.239.145]) by mails.dpdk.org (Postfix) with ESMTP id C0E174025D; Sun, 11 Feb 2024 20:07:49 +0100 (CET) Received: from mail-nwsmtp-smtp-production-main-37.myt.yp-c.yandex.net (mail-nwsmtp-smtp-production-main-37.myt.yp-c.yandex.net [IPv6:2a02:6b8:c12:291a:0:640:791e:0]) by forward501b.mail.yandex.net (Yandex) with ESMTPS id D67F460E96; Sun, 11 Feb 2024 22:07:48 +0300 (MSK) Received: by mail-nwsmtp-smtp-production-main-37.myt.yp-c.yandex.net (smtp/Yandex) with ESMTPSA id k7rBH2BHbKo0-SV0UONSF; Sun, 11 Feb 2024 22:07:47 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1707678467; bh=nVdBYImoiEc1GZ7y/pz4JAU7vvcTku4p4VvAWjY+0Tg=; h=From:In-Reply-To:Cc:To:Date:References:Subject:Message-ID; b=PGjoagKICF5FSssqHaFSgWaZVfTI+kqJ8qJFO9Qerusjku5IUVmNoNY/Unq86qNXF RTXdI55K0l78PWovVNUHXD5o3LilpEvzIirRaqO/I0X5IxIkZ9CwFyZSsqLBcJ3ZVA wgN1aPl1E7z12C9R20lnv6bU6RSVw1CTmLxbZ1VE= Authentication-Results: mail-nwsmtp-smtp-production-main-37.myt.yp-c.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <59d49453-83dc-4fee-ad65-f126e94417ce@yandex.ru> Date: Sun, 11 Feb 2024 19:07:45 +0000 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Minutes of Technical Board meeting 07-February-2024 Content-Language: en-US, ru-RU References: <4701850e-eb7c-47b8-a58d-c9d82bf9d125@yandex.ru> To: "dev@dpdk.org" Cc: "techboard@dpdk.org" From: Konstantin Ananyev In-Reply-To: <4701850e-eb7c-47b8-a58d-c9d82bf9d125@yandex.ru> X-Forwarded-Message-Id: <4701850e-eb7c-47b8-a58d-c9d82bf9d125@yandex.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 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 . 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.