Now that the tswg kernel module is under kernel/linux, the tests and
scripts that build it default to that tree rather than a separate
~/src/tslinux checkout, and the scripts find the tailscale.com
checkout they're in. TSWG_DIR and TAILSCALE_DIR still override them.
Also rename the module's COPYING to LICENSE, give the ML-KEM test the
repo's license header (and skip it without a C compiler, now that it
runs with the rest of the module's tests), and update DESIGN.md for
the new layout, which no longer has a pristine upstream/ copy.
Updates #426
Signed-off-by: Brad Fitzpatrick <[email protected]>
Change-Id: Ifcd99dd6d2197550d9c4abd13d4d4d80ed26dc60
subnetbench.sh runs tailscale.com's TestLeanSubnetRouter on the EC2
instances for each router CPU count given. ec2.sh now turns off source
and destination checks on its instances, so that one can forward as a
subnet router does, and installs nftables (for the router's masquerade).
DESIGN.md records the results: with 4 clients, tswg as the subnet
router forwards 2.1x (4 CPUs) to 3.2x (8 CPUs) what wireguard-go does,
which uses about 3 CPUs however many it has, at the least CPU per byte
of any tunnel, and reaches the 25 Gbps link at 16 CPUs. Zero-copy
receive was tried there and was 7% worse, so isn't in.
Updates #426
Signed-off-by: Brad Fitzpatrick <[email protected]>
Change-Id: I6b1da8bb8eaa17f9b20cbe36896426411b8b905f