mirror of
https://github.com/GNS3/gns3-server.git
synced 2026-11-21 05:35:15 +02:00
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:
6 files changed
+264
-145
No files matched your search
@@ -139,8 +139,9 @@ flowchart LR
|
||||
subgraph GQB["gqB — egress chain (clsact, then netem)"]
|
||||
S5["eBPF prio 1"]
|
||||
S6["bpf_drop prio 10-99"]
|
||||
S7["netem"]
|
||||
S7["netem qdisc"]
|
||||
end
|
||||
T["capture / markers"]
|
||||
end
|
||||
subgraph QPB["QEMU B — userspace"]
|
||||
S8["tap fd to QEMU"]
|
||||
@@ -149,17 +150,19 @@ flowchart LR
|
||||
S9["NIC receives"]
|
||||
end
|
||||
S1 -->|"virtio"| S2
|
||||
S2 --> S3
|
||||
S2 -->|"tap fd, copy 1: user→kernel"| S3
|
||||
S3 --> G1
|
||||
G1 -->|"PAUSE 0x01"| D
|
||||
G1 -->|"0xfffd passes"| S4
|
||||
S4 --> S5
|
||||
S5 --> S6 --> S7
|
||||
S7 --> S8
|
||||
S7 -->|"tap fd, copy 2: kernel→user"| S8
|
||||
S8 -->|"virtio IRQ"| S9
|
||||
S3 -. "AF_PACKET tap" .-> T
|
||||
S7 -. "AF_PACKET tap" .-> T
|
||||
```
|
||||
|
||||
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 taps observe both anchors but never a clsact-dropped frame.
|
||||
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 taps observe both anchors but never a clsact-dropped frame. Copies 1–2 are the whole path's only kernel/user crossings — both halves of the emulation's own TAP-fd leg (QEMU A's write, QEMU B's read); every stage between them runs in the kernel.
|
||||
|
||||
## Why a TAP works like a veth host end
|
||||
|
||||
|
||||
Reference in new issue
Block a user