Separate the instructions from the measurements The instruction pages had this testbed in them. A sample attach showed an interface the page had not told anyone to use, the scheduling note appealed to the testbed as though a reader knew what that was, and the troubleshooting page talked about a full mesh, which is this project word for its own fabric and not something anyone else has. The measurement pages keep their numbers, which is the point of them, but now say what travels to another machine. Per-frame costs do; packets per second belong to one NIC and one CPU. Session counts are given out of 64 because that is the fabric they were taken on, and what matters is whether any session was lost rather than the denominator. Also says what native and generic attach mean, since the sample output prints one of them and nothing explained it.
Seed the wiki: deployment, limitations, conformance, kernels, security, testing The README was cut back to what a reader needs first. This is the rest of it: the deployment notes and the reserved-port trap, the deviations from stock bfdd and from the RFC, the kernels the object is known to load on, the threat model and the flood measurements, and what each test suite covers and needs.