Commit 4e67d876 authored by Ilpo Jrvinen's avatar Ilpo Jrvinen Committed by David S. Miller

[TCP]: NAGLE_PUSH seems to be a wrong way around

The comment in tcp_nagle_test suggests that. This bug is very
very old, even 2.4.0 seems to have it.
Signed-off-by: default avatarIlpo Jrvinen <ilpo.jarvinen@helsinki.fi>
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
parent 52d34081
...@@ -1162,8 +1162,7 @@ int tcp_may_send_now(struct sock *sk) ...@@ -1162,8 +1162,7 @@ int tcp_may_send_now(struct sock *sk)
return (skb && return (skb &&
tcp_snd_test(sk, skb, tcp_current_mss(sk, 1), tcp_snd_test(sk, skb, tcp_current_mss(sk, 1),
(tcp_skb_is_last(sk, skb) ? (tcp_skb_is_last(sk, skb) ?
TCP_NAGLE_PUSH : tp->nonagle : TCP_NAGLE_PUSH)));
tp->nonagle)));
} }
/* Trim TSO SKB to LEN bytes, put the remaining data into a new packet /* Trim TSO SKB to LEN bytes, put the remaining data into a new packet
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment