io_uring in the Automotive World
summary
io_uring is evaluated for media indexing and software-update and RPC hotspots and shows concrete wins when operations are chained or resources are pre-registered: example CAN-over-WLAN bridge reduces two syscalls to one (roughly 200→100 syscalls at high packet rates). Android 13 already uses io_uring for OTA snapshot merging. Limitations block wins: readdir/llseek aren’t upstreamed, many BSPs lag kernel ≥5.1, and libraries like taglib use sync lseek/read so existing code often shows no speedup.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 0:35About KPIT
- 0:58Agenda
- 1:20Thank you Stefano Garcia
- 1:41Primary Goal
- 2:48What is iouring
- 3:24Traditional IO model
- 4:46IO Ring
- 5:45Submission Queue Entry
- 7:35Performance Benefits
- 12:46Android
- 13:36Use Cases
- 13:57Media Indexing
- 16:09Container Based Cockpit
- 16:52Software Update
- 18:38Binder RPC
- 21:10Other RPCs
- 22:46Ethernet WLAN Bridge
- 25:24Other Use Cases
- 26:24Challenges
- 28:07Taglib
- 32:33Conclusion
related talks
46mRevamping ioctl with io_uring
19mExperiences With Integration of Io_uring Into gRPC-C++
51mJourney to the End of Linux IO APIs (d…)
37mIndustrial IO and You- Nonsense Hacks!
59mThe Wild West of post-POSIX IO Interfaces
45mJourney to the end of Linux IO APIs (from poll to io_uring)
19mI/O Passthru: Upstreaming a flexible and efficient I/O Path in Linux
44mIndustrial I/O and You: Nonsense Hacks!