mirror of
https://github.com/slackhq/nebula.git
synced 2026-11-16 20:26:52 +01:00
tun: Keep relayed data on the reader transmit path
The sticky gate only drains socket submissions, so moving relay data between reader and staged sender CPUs can reorder packets on independent NIC queues. Keep relayed batches on the reader with separate, shared counter reservations while preserving the direct gate and sender affinity. Cover gate switches, oversized relay credit, mixed direct placement and stalled shared-tunnel reservations. Add Forgejo build, test, race, crypto, lint and artifact jobs on incus-docker.
This commit is contained in:
1 parent
5cbbba254e
commit
a784af4026
6 files changed
+307
-26
No files matched your search
@@ -18,6 +18,8 @@ import (
|
||||
// times 64 KiB with GRO, and the count keeps up to 384 entries in flight in four to six slots: six and 24 MiB at
|
||||
// listen.batch=64.
|
||||
// tun.staged.tx_slots and rx_slots override the counts. Small-MSS TX arenas can grow.
|
||||
// Relay data stays on the tun reader, regardless of the TX gate, so it never switches between reader and sender
|
||||
// NIC queues. Direct data keeps its adaptive placement; relay and direct batches both share tunnel counter credit.
|
||||
//
|
||||
// Metrics are registered only for active pipelines. flow.{tx,rx}.batches counts reads handed to the ordered stage and
|
||||
// flow.{tx,rx}.inline those the reader handled itself (TX inline also counts oversized reads); their rates show
|
||||
|
||||
Reference in new issue
Block a user