On 2016/6/28 12:57, Eric Dumazet wrote:
> On Tue, 2016-06-28 at 12:40 +0800, Tan Xiaojun wrote:
>> Hi everyone,
>>
>> I'm sorry to bother you. But I was confused.
>>
>> The IP ID check (flush_id) in inet_gro_receive is only used by
>> tcp_gro_receive, and in tcp_gro_receive we have
On 2016/6/28 12:57, Eric Dumazet wrote:
> On Tue, 2016-06-28 at 12:40 +0800, Tan Xiaojun wrote:
>> Hi everyone,
>>
>> I'm sorry to bother you. But I was confused.
>>
>> The IP ID check (flush_id) in inet_gro_receive is only used by
>> tcp_gro_receive, and in tcp_gro_receive we have
On Tue, 2016-06-28 at 12:40 +0800, Tan Xiaojun wrote:
> Hi everyone,
>
> I'm sorry to bother you. But I was confused.
>
> The IP ID check (flush_id) in inet_gro_receive is only used by
> tcp_gro_receive, and in tcp_gro_receive we have tcphdr check to ensure
> the order of skbs,
>
On Tue, 2016-06-28 at 12:40 +0800, Tan Xiaojun wrote:
> Hi everyone,
>
> I'm sorry to bother you. But I was confused.
>
> The IP ID check (flush_id) in inet_gro_receive is only used by
> tcp_gro_receive, and in tcp_gro_receive we have tcphdr check to ensure
> the order of skbs,
>
Hi everyone,
I'm sorry to bother you. But I was confused.
The IP ID check (flush_id) in inet_gro_receive is only used by
tcp_gro_receive, and in tcp_gro_receive we have tcphdr check to ensure the
order of skbs,
like below:
flush |= (__force int)(th->ack_seq ^
Hi everyone,
I'm sorry to bother you. But I was confused.
The IP ID check (flush_id) in inet_gro_receive is only used by
tcp_gro_receive, and in tcp_gro_receive we have tcphdr check to ensure the
order of skbs,
like below:
flush |= (__force int)(th->ack_seq ^
6 matches
Mail list logo
