Date: Sun, 1 Sep 2013 13:45:55 -0700 From: Adrian Chadd <adrian@freebsd.org> To: "Alexander V. Chernikov" <melifaro@ipfw.ru> Cc: Jack F Vogel <jfv@freebsd.org>, "Justin T. Gibbs" <gibbs@freebsd.org>, Alan Somers <asomers@freebsd.org>, "net@freebsd.org" <net@freebsd.org> Subject: Re: Flow ID, LACP, and igb Message-ID: <CAJ-Vmo=%2B__t_8xMsVjtz_ZeKEDyQHRb_kDikEVJO%2Bj2iFZYsgw@mail.gmail.com> In-Reply-To: <5222F661.1090601@ipfw.ru> References: <D01A0CB2-B1E3-4F4B-97FA-4C821C0E3FD2@FreeBSD.org> <5222F661.1090601@ipfw.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
> Not sure about igb, but ixgbe (according to advanced RX descriptor > format, 7.1.6.2 @ 82599 datasheet) can provide 'real' RSS value which > can be used in m_flowid instead of NIC queue id. > > (And, by the way, another RSS-related problem: > there are cases when setting flowid does more harm, for example - > PPPoE frames always being received at Q0. > Partially this can be solved by analyzing RSS type from the same RX > descriptor format (e.g. don't set flowid for RSS type 0x0), but there > are other cases like GRE tunneling (where you probably want to perform > deeper inspection in SW). > > So, can we have some kind of per-NIC sysctl disabling setting flowid > on given port? > > (Yes, this should be in some kind of `ethtool` binary but we still > don't have it..) > ) > What specifically are you asking for? Disabling the flowid tagging of mbufs? Or changing the LACP hashing? You can configure LACP to not use the flowid from the NIC and do the hashing yourself. -adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=%2B__t_8xMsVjtz_ZeKEDyQHRb_kDikEVJO%2Bj2iFZYsgw>