| commit | 407ef1de03e87225d75a9bed271f35ea6880f5f1 | [log] [tgz] |
|---|---|---|
| author | Ilpo Järvinen <ilpo.jarvinen@helsinki.fi> | Sun Dec 02 00:47:57 2007 +0200 |
| committer | David S. Miller <davem@davemloft.net> | Mon Jan 28 14:55:40 2008 -0800 |
| tree | 5003ff9db585997fceda75340f4631c311b0fe51 | |
| parent | bce392f3b02755a8c615d4ced3d3b9cb1d9e3648 [diff] |
[TCP]: Remove superflucious FLAG_DATA_SACKED To get there, highest_sack must have advanced. When it advances, a new skb is SACKed, which already sets that FLAG. Besides, the original purpose of it has puzzled me, never understood why LOST bit setting of retransmitted skb is marked with FLAG_DATA_SACKED. Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> Signed-off-by: David S. Miller <davem@davemloft.net>