On Tue, Jan 08, 2019 at 06:12:24PM -0800, Yuchung Cheng wrote:
> The existing BPF TCP initial congestion window (TCP_BPF_IW) does not
> to work on (active) Fast Open sender. This is because it changes the
> (initial) window only if data_segs_out is zero -- but data_segs_out
> is also incremented on
On 1/8/19, 6:13 PM, "netdev-ow...@vger.kernel.org on behalf of Yuchung Cheng"
wrote:
The existing BPF TCP initial congestion window (TCP_BPF_IW) does not
to work on (active) Fast Open sender. This is because it changes the
(initial) window only if data_segs_out is zero -- but data_se
The existing BPF TCP initial congestion window (TCP_BPF_IW) does not
to work on (active) Fast Open sender. This is because it changes the
(initial) window only if data_segs_out is zero -- but data_segs_out
is also incremented on SYN-data. This patch fixes the issue by
proerly accounting for SYN-da