Hi Yuchung,
Sorry for the confusion. The test case was adapted from an old DSACK
test case (i.e., forget to remove something).
Attached is a new and simple one. Thanks
On Wed, Jul 19, 2017 at 2:31 PM, Yuchung Cheng wrote:
> On Tue, Jul 18, 2017 at 2:36 PM, Wei Sun wrote:
>>
Hi there,
We find a buggy behavior when using Linux TCP Reno and HTCP in low
bandwidth or highly congested network environments.
In a simple word, their undo functions may mistakenly double the cwnd,
leading to a more aggressive behavior in a highly congested scenario.
The detailed reason:
The
Hi there,
we find a special case for Linux TCP undo operations where
tp->snd_cwnd could be extremely large (e.g., 4294967294) by two
consecutive cwnd undo operations when using
reno/veno/vegas/highspeed/HTCP/yeah/westwood/hybla/illinois/scalable/lp
congestion control algorithms in the latest long-
