diff options
author | Ilpo Järvinen <ilpo.jarvinen@helsinki.fi> | 2013-02-04 02:14:25 +0000 |
---|---|---|
committer | Ben Hutchings <ben@decadent.org.uk> | 2013-02-20 03:15:38 +0000 |
commit | 4670ea19f63e7db7ca352e68e120e82e3c135fbb (patch) | |
tree | 39fb90526d5cb36b5a8f4311a1e0096c0bc300f5 /net/nfc | |
parent | 50a3d765940ac3f88b82b7e6dca49824c4ad78fa (diff) |
tcp: fix for zero packets_in_flight was too broad
[ Upstream commit 6731d2095bd4aef18027c72ef845ab1087c3ba63 ]
There are transients during normal FRTO procedure during which
the packets_in_flight can go to zero between write_queue state
updates and firing the resulting segments out. As FRTO processing
occurs during that window the check must be more precise to
not match "spuriously" :-). More specificly, e.g., when
packets_in_flight is zero but FLAG_DATA_ACKED is true the problematic
branch that set cwnd into zero would not be taken and new segments
might be sent out later.
Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi>
Tested-by: Eric Dumazet <edumazet@google.com>
Acked-by: Neal Cardwell <ncardwell@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Diffstat (limited to 'net/nfc')
0 files changed, 0 insertions, 0 deletions