DPDK Summit 2026

Events (jobs) in Eventdev are non-preemptive, and thus must be relatively short run time.

One way to deal with this issue is to split large jobs into multiple events.

For legacy code, originally design for POSIX threads, such an exercise may be costly. Also, for certain domains, being able to retain the stack between invocations (events) may results in a simpler program.

This talk briefly introduce this topic and discuss an Ericsson prototype coroutine library running on top of Eventdev, allowing for a code written for a thread-like, cooperative multi-tasking programming model to coexist with native event-driven programs running on the same DPDK lcores, making the coroutine library in combination the event device a task/thread scheduler.

Note: I have not reviewed the two-hour "Inclusive Speaker Orientation" training. If this is mandatory, please ignore this submission.