1fb466941a
Instead of creating a go routine to process each incoming datagram from the tunnel, a single consumer (the demuxer) will process each of the datagrams in serial. Registration datagrams will still be spun out into separate go routines since they are responsible for managing the lifetime of the session once started via the `Serve` method. UDP payload datagrams will be handled in separate channels to allow for parallel writing inside of the scope of a session via a new write loop. This channel will have a small buffer to help unblock the demuxer from dequeueing other datagrams. ICMP datagrams will be funneled into a single channel across all possible origins with a single consumer to write to their respective destinations. Each of these changes is to prevent datagram reordering from occurring when dequeuing from the tunnel connection. By establishing a single demuxer that serializes the writes per session, each session will be able to write sequentially, but in parallel to their respective origins. Closes TUN-9882 |
||
|---|---|---|
| .. | ||
| v3 | ||
| constants.go | ||
| conversion.go | ||
| datagram.go | ||
| datagram_test.go | ||
| datagramv2.go | ||
| metrics.go | ||
| param_unix.go | ||
| param_windows.go | ||
| safe_stream.go | ||
| safe_stream_test.go | ||
| tracing.go | ||