summaryrefslogtreecommitdiffstats
path: root/net/bluetooth
diff options
context:
space:
mode:
authorIlpo Järvinen <ilpo.jarvinen@helsinki.fi>2008-12-03 21:24:48 -0800
committerDavid S. Miller <davem@davemloft.net>2008-12-03 21:24:48 -0800
commitf8269a495a1924f8b023532dd3e77423432db810 (patch)
tree73b5f7b9e059a79b890c53572e0e048a2078577d /net/bluetooth
parent5176da7e5318669220e4d2fa856223054a3efc9f (diff)
downloadop-kernel-dev-f8269a495a1924f8b023532dd3e77423432db810.zip
op-kernel-dev-f8269a495a1924f8b023532dd3e77423432db810.tar.gz
tcp: make urg+gso work for real this time
I should have noticed this earlier... :-) The previous solution to URG+GSO/TSO will cause SACK block tcp_fragment to do zig-zig patterns, or even worse, a steep downward slope into packet counting because each skb pcount would be truncated to pcount of 2 and then the following fragments of the later portion would restore the window again. Basically this reverts "tcp: Do not use TSO/GSO when there is urgent data" (33cf71cee1). It also removes some unnecessary code from tcp_current_mss that didn't work as intented either (could be that something was changed down the road, or it might have been broken since the dawn of time) because it only works once urg is already written while this bug shows up starting from ~64k before the urg point. The retransmissions already are split to mss sized chunks, so only new data sending paths need splitting in case they have a segment otherwise suitable for gso/tso. The actually check can be improved to be more narrow but since this is late -rc already, I'll postpone thinking the more fine-grained things. Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/bluetooth')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud