docs(iou): record the IOU kernel datapath and its spec

* docs/features/iou-kernel-datapath.md: architecture (one irreducible
  userspace hop on the fabric leg, kernel link segment), datapath
  selection, the anchor lifecycle with the reverse-of-QEMU stop order,
  capture/markers/filters, relay fallback, and the verified numbers (an
  isolated server with two IOU nodes behind a fake ELF image, the test
  playing the IOL fabric: 64/64 kernel, 62/62 relay).
* docs/design/ubridge-iol-tap-anchor-spec.md: delivered — implemented on
  the ubridge fork's feature/iol-tap-anchor branch (both commands, the
  listener hardening, plus releasing every port NIO on iol_bridge delete
  even when the bridge was not running), with the implementation notes
  that came back (208 vs the older 214 for a missing bridge; one perror
  line per frame dropped on a down anchor).
* The Docker/QEMU feature docs point at it from their roadmaps.
This commit is contained in:
YueGuobin committed 2026-10-06 00:21:09 +08:00
1 parent f23c3bb6e6
commit 3b8172cbc8
4 files changed
+452 -3

No files matched your search

+6 -2
View File
@@ -367,8 +367,12 @@ enable_kernel_datapath = True
Intended to grow into the global datapath switch as IOU / Dynamips migrate to
kernel bridges. **QEMU has landed** on the same pattern (persistent TAP anchor
enslaved into the per-link bridge, zero relay) — see
`docs/features/qemu-kernel-datapath.md`; the shared half of this document's
compute machinery now lives in `gns3server/compute/kernel_datapath.py`.
`docs/features/qemu-kernel-datapath.md` — and **IOU after it**
(`docs/features/iou-kernel-datapath.md`; the fabric terminator in uBridge
gained a TAP-terminated port, `iol_bridge add_nio_tap`, specified in
`docs/design/ubridge-iol-tap-anchor-spec.md`). The shared half of this
document's compute machinery now lives in
`gns3server/compute/kernel_datapath.py`.
## Verification