tcp: Do not check flush when comparing options for GRO
There is no need to repeatedly check flush when comparing TCP options for GRO as it will be false 99% of the time where it matters. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
parent
9aaa156cf9
commit
a2a804cddf
|
@ -2570,7 +2570,7 @@ found:
|
||||||
flush |= (flags ^ tcp_flag_word(th2)) &
|
flush |= (flags ^ tcp_flag_word(th2)) &
|
||||||
~(TCP_FLAG_CWR | TCP_FLAG_FIN | TCP_FLAG_PSH);
|
~(TCP_FLAG_CWR | TCP_FLAG_FIN | TCP_FLAG_PSH);
|
||||||
flush |= th->ack_seq ^ th2->ack_seq;
|
flush |= th->ack_seq ^ th2->ack_seq;
|
||||||
for (i = sizeof(*th); !flush && i < thlen; i += 4)
|
for (i = sizeof(*th); i < thlen; i += 4)
|
||||||
flush |= *(u32 *)((u8 *)th + i) ^
|
flush |= *(u32 *)((u8 *)th + i) ^
|
||||||
*(u32 *)((u8 *)th2 + i);
|
*(u32 *)((u8 *)th2 + i);
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue