Machine reable description for netlink protocols (YAML?)
summary
Proposal: a YAML-based, machine-readable description for netlink protocols that lets tools auto-serialize and deserialize messages and generate kernel artifacts. Uses a YAML family spec consumed by a ynl generic library to turn attribute IDs into names, emit operation and policy tables, and generate uapi headers and docs. Prototype code and two RFCs exist; it already covers new families and works with ethtool and devlink with minor quirks; mapping IDs back to names makes kernel "point-at-attribute" errors user-readable and Python support is imminent.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 5:20Netlink basics and challenges
- 7:04YAML for Netlink protocols
- 17:15YAML specification details
- 23:04YAML benefits and limitations
- 26:49Q&A on Netlink and YAML
- 27:16Transition to BPF talk
- 27:48Motivation for TC BPF data path
- 31:04Debugging the staging environment outage
- 34:11BPF links and ownership model
- 41:15TC object model and BPF links
- 44:11Reference design for TC BPF data path
- 50:33BPF links integration
- 51:59Q&A on TC BPF and BPF links
- 58:10Break
- 58:33Introduction to packet classification
- 59:18Packet classification algorithms
- 1:04:23Tuple space search limitations
- 1:11:54Tuple merge optimizations
- 1:17:14New BPF map API example
- 1:22:15Kernel changes and BTF
- 1:25:45Performance numbers and trade-offs
- 1:30:49Q&A on BPF map API and LPM
related talks
24mDeclare your Linux Network state!
24mModern network configuration on Linux
30mFrom YANG To YAML: How We Tamed the 5G Configuration Beast
30mUsing Python to design, configure, and measure large-scale networks
43mThe New Network Engineer’s CLI: Network APIs, Data Structures & Data Models
16mHigh-level Programming for Application Networks
46mNetworking: From the Ethernet MAC to the Link Partner
47mDeep Programmability: A New Lens on Networking