The Sched app allows you to build your schedule but is not a substitute for your event registration. You must be registered for DPDK Summit 2026 to participate in the sessions. Please go to the event registration page to purchase a registration.
Please note: This schedule is automatically displayed in Central European Time.To see the schedule in your preferred timezone, please select from the drop-down at the bottom of the menu to the right.
The schedule is subject to change.
Sign up or log in to add sessions to your schedule and sync them to your phone or calendar.
DPDK library supports cryptodev which mainly deals with static keys. It does not have support for any dynamic internet key exchange. In this talk, we present an approach to integrate DPDK enabled cloud native router with opensource strongswan to support IKE for IPSec. A custom packet processing pipeline will also be presented where dedicated encryption/decryption cores are reserved and packets are steered to it depending on the routing policy.
Kiran is a Principal engineer in Juniper networks with over 18 years of experience in the SDN/cloud/datapath domain. He is the datapath architect and is working on Juniper Cloud native router (datapath) from last 2 years. He is currently focusing of software routing in the 5G space... Read More →
DPDK is used as the packet-ingest layer for a traffic monitoring system feeding an internal DPI engine. Today, throughput is maximized by tuning for a specific server/NIC/OS combination, but this reduces portability and increases operational effort.
This lightning talk discusses the throughput impact observed when moving toward a more “generic” deployment. Results are presented for: (1) optimized (“native”) vs portable (“generic”) builds, (2) CPU isolation, (3) hugepage configuration and (4) PMD/driver configuration.
Software Developer, ipoque, a Rohde & Schwarz company
Harald Bunke is a software developer at ipoque working on network traffic analysis and Deep Packet Inspection (DPI) systems. In this role, he focuses on packet-ingest and performance aspects of DPDK-based application on Linux, supporting deployment and benchmarking across different hardware and runtime configurations... Read More →
As a long-time DPDK developer, I am more used to working on code WITHIN DPDK rather than writing apps USING DPDK. On the odd occasion, when I do need to create an end-user app using DPDK, there are a number of the additional little libraries and tools in DPDK that I reach for to improve the DPDK app development and debug process. These include the cmdline library (including using the new script for cmdline generation), configfile library, telemetry support, and others. While most of these are not likely to be new to many developers, the content here may prove helpful to anyone starting out with green-field DPDK development, or putting together quick apps for packet processing using DPDK.
Bruce Richardson is well-known in the DPDK community as a long-time contributor to the project, and member of the technical board. As part of his day-job in Intel, he makes project contributions across a range of areas in DPDK, as well as being involved in patch reviews and discussions... Read More →
Currently, the standard development workflow for DPDK goes something like this: A developer wants to add a new feature or resolve a bug in DPDK, so they write a patch, run the DPDK unit tests against it, and then if those are passing, send it off to the mailing list, where it will get picked up by CI labs that run end to end testing on real hardware using the DPDK Test Suite. Although this solution works fairly well, DPDK developers may also gain some valuable speed and confidence by directly integrating the DPDK Test Suite into their local development workflow. So, I will “demo” the following sequence. First apply a patch to DPDK which either resolves or breaks some DPDK functionality. Then, pass this new DPDK source into the DPDK Test Suite, executing a testcase/testcases on a minimal DTS setup. Then, overview the results produced by DTS, and highlight how the patch applied in step 1 resolved/broke functionality tracked by the testcase/testcases being run. Specifically, I will demonstrate this workflow through the new Flow Offload Testsuite that is arriving to DPDK in DPDK version 26.03.
