From a0d76b30c0435bf9af8643b5382c79590192c2cc Mon Sep 17 00:00:00 2001 From: YueGuobin Date: Fri, 2 Oct 2026 19:30:29 +0800 Subject: [PATCH] docs(iou): record the in-repo e2e coverage The Verified section only described the /tmp driver with a fake IOU image; the repository suite now carries the same scenario with real routers on a real L3 image. --- docs/features/iou-kernel-datapath.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/features/iou-kernel-datapath.md b/docs/features/iou-kernel-datapath.md index c1b531a98..a0fc2df66 100644 --- a/docs/features/iou-kernel-datapath.md +++ b/docs/features/iou-kernel-datapath.md @@ -142,6 +142,14 @@ qdiscs, userspace `delay` at 100.7 ms, suspend via the synthetic frequency_drop, `iol_bridge start_capture`), which is also the regression net for the port-coordinate capture restore this work touched. +The repository's live e2e suite carries the same scenario with **real +IOU routers** (`tests/e2e/test_iou_kernel_datapath.py`, pytest marker +`e2e`): a real L3 IOU image provides the fabric and the real IOS CLI on +the server's telnet console, driving anchors-born-with-the-node, real ICMP +through the port bridge, netem delay, suspend, capture, link +delete/re-create, node stop/start rewiring, the serial link staying on the +relay, and a relay negative control. + The uBridge side passed its own 30/30 (`tests/iol/test_tap_anchor.py` in the fork), including the DOWN-anchor resilience and kernel-bridge interop this design depends on.