docs: dynamips kernel-datapath diagram suite, unified frame-path form across the family

The dynamips doc gets the full suite: anatomy (anchors reached by the
hypervisors' TAP fds, uBridge's AF_PACKET-tap / tc-qdisc sidebands), a
one-way copy-numbered relay comparison (six kernel/user crossings per
way against the kernel datapath's two TAP-fd legs), a staged walkthrough
(reserved-range diamond, egress clsact chain, capture/markers observation
sideband, copies 1-2) and a control sequence of real commands in real
order (hypervisor fd first, capture before markers, carrier last; router
handlers, not computes, as the per-node participants).

The four sibling frame paths are unified on the same form: netem qdisc
node labels, one capture/markers node outside the stages with AF_PACKET
tap edges anchored at ingress and post-chain egress, copy numbering
wherever the trace crosses the kernel/user boundary (qemu's two TAP-fd
legs, iol-docker's six socket/TAP legs), stage subgraphs with role-noted
titles everywhere (iol-docker restructured from its flat chain, iou's
chA/tapA variants folded into the canonical shapes).

The documentation skill records the rules as v3.1.0: four diagram kinds
(anatomy / comparison / control sequence / walkthrough), one step per
node, dashed sidebands per role with meaningful direction, numbered
crossings when copies are the point, glossary before the first diagram.
This commit is contained in:
YueGuobin committed 2026-10-06 00:21:10 +08:00
1 parent d0773aabea
commit 74010b9abd
6 files changed
+264 -145

No files matched your search

+5 -6
View File
@@ -115,10 +115,8 @@ flowchart LR
subgraph UBA["uBridge A — userspace"]
S2["relay"]
end
subgraph GIA["giA — ingress"]
subgraph GIA["giA — ingress (its egress chain serves B→A)"]
S4["ingress"]
chA["clsact + netem chain"]
tapA["AF_PACKET tap: capture + markers"]
end
subgraph BRP["per-link bridge"]
G1{"reserved 01:80:c2?"}
@@ -128,7 +126,7 @@ flowchart LR
subgraph GIB["giB — egress chain (clsact, then netem)"]
S6["eBPF prio 1"]
S7["bpf_drop prio 10-99"]
S8["netem"]
S8["netem qdisc"]
end
subgraph UBB["uBridge B — userspace"]
S9["relay"]
@@ -147,8 +145,9 @@ flowchart LR
S8 -->|"copy 4: kernel→user"| S9
S9 -->|"copy 5: user→kernel"| mbxB
mbxB -->|"copy 6: kernel→user"| S11
S4 -.->|"serves B→A"| chA
S4 -.->|"observes tx + rx"| tapA
tap["capture / markers"]
S4 -.->|"AF_PACKET tap"| tap
S8 -.->|"AF_PACKET tap"| tap
```
What each stage drops: the reserved-range gate passes LACP, LLDP, 802.1X and STP per the port mask but never PAUSE/PFC (Link-local frames below); the clsact/netem stages drop or impair per the installed filters (Capture, markers, filters below); the AF_PACKET tap — capture and markers ride it, installed at whichever end captures — observes both directions of the link through its anchor (tx/rx signal pairs) but never a clsact-dropped frame. The crossings do not disappear on this datapath: each leg still crosses the kernel/user boundary three times (`sendto`/`recvfrom` on the fabric, then the TAP write — the B leg mirrors them, six per one-way frame, the same count as the relay); what moves into the kernel is the link segment — no UDP tunnel, no protocol-stack pass — and with it the impairment chain. A fabric → anchor → bridge → anchor → fabric round trip measures ≈0.2 ms (Verified below).