docs(dynamips): record the kernel datapath and its live verification

New features/dynamips-kernel-datapath.md: the anchor model (persistent TAP
per Ethernet port, the hypervisor opens it with nio create_tap), port
selection via the adapter registry, the anchor lifecycle with QEMU's stop
order and the stop-is-not-close semantics, link operations, capture/
markers/filters, the relay fallback, the live e2e results, configuration
and the roadmap (Ethernet switch next). The IOU and QEMU roadmaps note
that Dynamips has landed.
This commit is contained in:
YueGuobin committed 2026-10-06 00:21:09 +08:00
1 parent 5c2c8cdb0c
commit 3910a6b585
3 files changed
+166 -6

No files matched your search

+7 -5
View File
@@ -169,8 +169,10 @@ enable_kernel_datapath = True
## Roadmap
Dynamips next (hypervisor-created taps, enslavable as they are), then the
Ethernet switch (its anchors are ubridge-owned by design) and the IOL Docker
node (same `bridge add_nio_tap` shape as this one). Cross-compute kernel
links need VXLAN/GENEVE encapsulation — deferred until every node type is
kernelized.
Dynamips has landed (see `dynamips-kernel-datapath.md` — the hypervisor
opens uBridge-created TAPs, the same shape QEMU uses). Next: the Ethernet
switch (its ports are already uBridge-owned TAPs; the kernel link should
attach the peer's anchor straight into the switch's per-node bridge), then
the IOL Docker node (same `bridge add_nio_tap` shape as this one).
Cross-compute kernel links need VXLAN/GENEVE encapsulation — deferred
until every node type is kernelized.