Searched hist:"01 f83d69844d307be2aa6fea88b0e8fe5cbdb2f4" (Results 1 – 1 of 1) sorted by relevance
| /linux/include/net/ |
| H A D | tcp.h | diff 2631b79f6cb8b634fe41b77de9c4add0ec6b3cae Wed Jun 29 01:06:48 CEST 2016 Seymour, Shane M <shane.seymour@hpe.com> tcp: increase size at which tcp_bound_to_half_wnd bounds to > TCP_MSS_DEFAULT
In previous commit 01f83d69844d307be2aa6fea88b0e8fe5cbdb2f4
the following comments were added:
"When peer uses tiny windows, there is no use in packetizing to sub-MSS
pieces for the sake of SWS or making sure there are enough packets in
the pipe for fast recovery."
The test should be > TCP_MSS_DEFAULT not >= 512. This allows low end
devices that send an MSS of 536 (TCP_MSS_DEFAULT) to see better network
performance by sending it 536 bytes of data at a time instead of bounding
to half window size (268). Other network stacks work this way, e.g. HP-UX.
Signed-off-by: Shane Seymour <shane.seymour@hpe.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
diff 01f83d69844d307be2aa6fea88b0e8fe5cbdb2f4 Wed Sep 15 19:27:52 CEST 2010 Alexey Kuznetsov <kuznet@ms2.inr.ac.ru> tcp: Prevent overzealous packetization by SWS logic.
If peer uses tiny MSS (say, 75 bytes) and similarly tiny advertised
window, the SWS logic will packetize to half the MSS unnecessarily.
This causes problems with some embedded devices.
However for large MSS devices we do want to half-MSS packetize
otherwise we never get enough packets into the pipe for things
like fast retransmit and recovery to work.
Be careful also to handle the case where MSS > window, otherwise
we'll never send until the probe timer.
Reported-by: ツ Leandro Melo de Sales <leandroal@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|