[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 20 Apr 2010 21:21:36 -0400 (EDT)
From: Mikulas Patocka <mpatocka@...hat.com>
To: David Miller <davem@...emloft.net>
cc: netdev@...r.kernel.org, kaber@...sh.net
Subject: Re: crash with bridge and inconsistent handling of NETDEV_TX_OK
On Tue, 20 Apr 2010, David Miller wrote:
> From: David Miller <davem@...emloft.net>
> Date: Tue, 20 Apr 2010 18:14:34 -0700 (PDT)
>
> > From: Mikulas Patocka <mpatocka@...hat.com>
> > Date: Tue, 20 Apr 2010 21:10:04 -0400 (EDT)
> >
> >> I see, but GRO is turned off on my interfaces, according to ethtool.
> >
> > GRO is just a flag bit, so it's possible that if your kernel is too
> > old ethtool will always show that it's off.
>
> Actually, looking back at your original report, are you confusing
> "large-receive-offload" as reported by ethtool with GRO?
>
> They are completely seperate things.
>
> "large-receive-offload" is LRO, whereas GRO is something done
> in software and something entirely different.
Posting once more. Both LRO and GRO are off. And it is default.
Mikulas
Offload parameters for eth0:
rx-checksumming: on
tx-checksumming: on
scatter-gather: on
tcp-segmentation-offload: off
udp-fragmentation-offload: off
generic-segmentation-offload: on
generic-receive-offload: off
large-receive-offload: off
Offload parameters for eth1:
rx-checksumming: on
tx-checksumming: on
scatter-gather: on
tcp-segmentation-offload: off
udp-fragmentation-offload: off
generic-segmentation-offload: on
generic-receive-offload: off
large-receive-offload: off
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists