On Thu, Sep 20, 2012 at 08:16:11PM +0200, Henning Brauer wrote:
> so, resurrecting, slighly updated diff.
>
> I need your help testing. This diff has a kinda high breakage
> potential, since there are quite a few output pathes. On the plus side
> breakage is easy to spot, since that'll result in b
On 2012/09/22 13:29, Camiel Dobbelaar wrote:
> On 21-9-2012 23:40, Stuart Henderson wrote:
> > $ ifconfig vr0 hwfeatures|head -2
> > vr0: flags=8b43
> > mtu 1500
> > hwfeatures=8017
> >
> > No problems noticed yet. (this is running i386).
> >
> > $ ifconfig vlan6 hwfeatures|head -2
> > v
On 21-9-2012 23:40, Stuart Henderson wrote:
> $ ifconfig vr0 hwfeatures|head -2
> vr0: flags=8b43 mtu
> 1500
> hwfeatures=8017
>
> No problems noticed yet. (this is running i386).
>
> $ ifconfig vlan6 hwfeatures|head -2
> vlan6: flags=8943 mtu 1500
> hwfeatures=0<>
>
> Is it rig
On 2012/09/20 20:16, Henning Brauer wrote:
> I need your help testing. This diff has a kinda high breakage
> potential, since there are quite a few output pathes. On the plus side
> breakage is easy to spot, since that'll result in bad checksums and
> thus these packets getting dropped. Should be a
so, resurrecting, slighly updated diff.
I need your help testing. This diff has a kinda high breakage
potential, since there are quite a few output pathes. On the plus side
breakage is easy to spot, since that'll result in bad checksums and
thus these packets getting dropped. Should be all or none
after just 15 months i got this finally working.
basically moving us to the assumption that there is some cksum offload
engine in each an every output path, calling the software engine very
late if we figure there is none. foremost this adds this logic to the
alternate output pathes like bridge, t
