Re: Issues with ixl(4)

So I've done some more testing, and it's definitely some kind of interaction between ixl & lagg, and maybe even ix & lagg. It doesn't matter if lagg is using "lacp" or "loadbalance" (with the switch set appropriately), it happens on both. I did find out that statically adding an arp entry for

Re: Issues with ixl(4)

On Wednesday, April 20, 2016, Dustin Marquess wrote: > I tried backing out that change and everything worked for a few minutes > and then started acting up again. Then I notice Sean Bruno's "TCP Packets > Drop!!!" email about LACP. I disabled LACP on the switch side and

Re: Issues with ixl(4)

I tried backing out that change and everything worked for a few minutes and then started acting up again. Then I notice Sean Bruno's "TCP Packets Drop!!!" email about LACP. I disabled LACP on the switch side and then changed the lagg config from "lacp" to "roundrobin", and so far so good. On the

Re: Issues with ixl(4)

On 2016-04-20, at 1:15, K. Macy wrote: > FWIW, NFLX sees performance close to that of cxgbe (by far the best > maintained, best performing FreeBSD 40G driver) with an iflib > converted driver. The iflib updated driver will be imported by 11 but > won't become the default driver

Re: Issues with ixl(4)

I haven't played with lagg+vlan+bridge, but I briefly evaluated XL710 boards last year (https://lists.freebsd.org/pipermail/freebsd-net/2015-October/043584.html) and saw very poor throughputs and latencies even in very simple setups. As far as I could figure it out, TSO/LRO wasn't being