On Tue, Mar 22, 2016 at 3:09 PM, Tom Herbert wrote:
> On Tue, Mar 22, 2016 at 2:45 PM, Alexander Duyck
> wrote:
>> On Tue, Mar 22, 2016 at 2:10 PM, Tom Herbert wrote:
>>> On Tue, Mar 22, 2016 at 1:20 PM, Alexander Duyck
>>> wrote:
On Tue, Mar 22, 2016 at 12:19 PM, Tom Herbert wrote:
>
On Tue, Mar 22, 2016 at 2:45 PM, Alexander Duyck
wrote:
> On Tue, Mar 22, 2016 at 2:10 PM, Tom Herbert wrote:
>> On Tue, Mar 22, 2016 at 1:20 PM, Alexander Duyck
>> wrote:
>>> On Tue, Mar 22, 2016 at 12:19 PM, Tom Herbert wrote:
In skb_segment the check of whether or not to perform the che
On Tue, Mar 22, 2016 at 2:10 PM, Tom Herbert wrote:
> On Tue, Mar 22, 2016 at 1:20 PM, Alexander Duyck
> wrote:
>> On Tue, Mar 22, 2016 at 12:19 PM, Tom Herbert wrote:
>>> In skb_segment the check of whether or not to perform the checksum on
>>> host was changed to not consider rather remote che
On Tue, Mar 22, 2016 at 1:20 PM, Alexander Duyck
wrote:
> On Tue, Mar 22, 2016 at 12:19 PM, Tom Herbert wrote:
>> In skb_segment the check of whether or not to perform the checksum on
>> host was changed to not consider rather remote checksum offload is
>> in use. In the case that can_checksum_pr
On Tue, Mar 22, 2016 at 12:19 PM, Tom Herbert wrote:
> In skb_segment the check of whether or not to perform the checksum on
> host was changed to not consider rather remote checksum offload is
> in use. In the case that can_checksum_protocol fails the checksum
> is computed regardless. __skb_udp_
In skb_segment the check of whether or not to perform the checksum on
host was changed to not consider rather remote checksum offload is
in use. In the case that can_checksum_protocol fails the checksum
is computed regardless. __skb_udp_tunnel_segment was modified in a
related patch to add NETIF_F_
