From 4869d309e122445ee43ab79e00bd3b1dfa9d9275 Mon Sep 17 00:00:00 2001 From: Stefano Brivio Date: Tue, 12 Oct 2021 22:56:36 +0200 Subject: [PATCH] doc: Fix up note about missing tcpi_snd_wnd in man page The behaviour without tcpi_snd_wnd changed: the only difference now is the advertised window, which corresponds to the queried sending buffer size. Signed-off-by: Stefano Brivio --- passt.1 | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/passt.1 b/passt.1 index df9892b..554d31d 100644 --- a/passt.1 +++ b/passt.1 @@ -695,13 +695,9 @@ option, see \fBtcp\fR(7). Before Linux 5.3, i.e. before Linux kernel commit 8f7baad7f035 ("tcp: Add snd_wnd to TCP_INFO"), the sending window (\fIsnd_wnd\fR field) is not available. -If the sending window cannot be queried, it will always be announced as a fixed -value to guest or target namespace (14 600 bytes, suggested by RFC 6928), and -segments received by guest or target namespace will be acknowledged as soon as -the corresponding payload is enqueued to the corresponding socket. The normal -behaviour is to acknowledge segments only as the remote peer acknowledges the -corresponding payload, in order to reflect the congestion control dynamic back -to the sender. This might affect throughput of TCP connections. +If the sending window cannot be queried, it will always be announced as the +current sending buffer size to guest or target namespace. This might affect +throughput of TCP connections. .SH LIMITATIONS