docs(iol): record the IOL runner container kernel datapath

The feature doc covers the architecture (one irreducible userspace hop
on the unix-socket leg; the link segment kernelized through the port
bridge's swappable TAP leg), the capability gate, the anchor lifecycle,
the swap flow, the inherited capture/markers/filters, the relay
fallback and the live verification — including the ensure-then-add
lesson (tap create is strictly create-only).

The other datapath docs' roadmaps catch up: the IOL runner container
has landed (and the ethernet-switch doc's stale 'cascade deferred'
exclusion from d2f8aba58 is corrected while there); the docker doc's
adapter table no longer rejects IOLDockerVM.
This commit is contained in:
YueGuobin committed 2026-10-06 00:21:09 +08:00
1 parent 72aa379e87
commit 02340f2ed3
6 files changed
+199 -17

No files matched your search

+3 -1
View File
@@ -151,5 +151,7 @@ enable_kernel_datapath = True
The Ethernet switch has landed (see `ethernet-switch-kernel-datapath.md` —
it absorbs the peer's anchor into its own kernel bridge; switch-to-switch
cascades and the IOL Docker node are next). Cross-compute kernel links need
cascades and the IOL runner container have landed too — see
`ethernet-switch-kernel-datapath.md` and
`iol-docker-kernel-datapath.md`). Cross-compute kernel links need
VXLAN/GENEVE encapsulation — deferred until every node type is kernelized.