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.
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.
