FW centric devices, NIC customization
summary
Modern NIC firmware contains half a million lines of core code and exposes roughly 600 configurable knobs, growing about 25% per year, so users must pick precise combinations (for example offload crypto engines) to avoid performance limits. Current kernel hooks (devlink) cover non‑volatile, runtime and per‑PF/port parameters but lack vendor extension usability, runtime debug control and a safe path for vendor‑specific flags; vendors ship Windows toolchains or out‑of‑tree drivers instead of standardized devlink parameters.
AI-written summary · about
chapters (7)
- 0:00Introduction to firmware devices
- 3:35Modern NIC complexity and knobs
- 10:28Current tool limitations for NICs
- 16:16Missing configurability and debug levels
- 20:14Need for vendor flexibility in standards
- 28:49Discussion on standardization efforts
- 31:38Q&A and closing remarks
related talks
40mOF-nodes, Fwnodes, Swnodes, Devlinks, Properties - Understanding How Devices...
43mBeyond Static Devicetrees: Implementing Runtime Hardware Dynamism in Ze...
44mLinux Kernel Developer Panel
44mModernizing the NAND Framework: The Big Picture
52mIn the Kernel Trenches: Mastering Ethernet Drivers on Linux
25mPCI Endpoint Drivers in Linux Kernel and How to Write One
01h 06mWhat's up in the land of the Linux kernel
41mBraiding Wires Into the Linux Network Stack - Recent Work on Embedded Networking