Issues with ixl(4)

[Dustin Marquess]

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 switch side it looks like member ports were randomly bounding in the
LACP bundle, and when I'd tcpdump an interface I wouldn't see anything
until another LACP&LLDP packet came in.

So something seems to be broken with lagg's LACP support recently.  The
good news is I don't think the route caching is causing this problem.  I'll
put it back in and retest to make sure though.

Thanks for the help!
-Dustin

On Tue, Apr 19, 2016 at 6:15 PM, K. Macy <kmacy at freebsd.org> wrote:

> On Mon, Apr 18, 2016 at 10:45 PM, Eggert, Lars <lars at netapp.com> wrote:
> > 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 performed (although
> enabled) and so I ran into packet-rate issues.
> >
> > I basically gave up and went with a different vendor. FWIW, the XL710
> boards in the same machines booted into Linux performed fine.
> >
>
> 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 until 11.1 for wont of QA resources at
> Intel.
>
> -M
>