Date: Sun, 20 May 2018 20:42:21 +0200 From: Harry Schmalzbauer <freebsd@omnilan.de> To: Stephen Hurd <shurd@llnw.com> Cc: mmacy@mattmacy.io, "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>, Stephen Hurd <shurd@freebsd.org>, Kevin Bowling <kevin.bowling@kev009.com> Subject: Re: iflib-if_em tests with HEAD and lagg panic [Was: Re: svn commit: r333338 - in stable/11/sys: dev/bnxt kern net sys] Message-ID: <b355ffcf-a514-aaeb-7a11-39e5d437b526@omnilan.de> In-Reply-To: <5AF5D1E6.2090301@omnilan.de> References: <201805072142.w47LgN1R041002@repo.freebsd.org> <5AF16B8B.7030703@omnilan.de> <CAK7dMtBkCvLgPVnsf%2BECcrdbKNvOShONeZ=vqvg3dJ5ZeuoP5w@mail.gmail.com> <5AF17134.7020602@omnilan.de> <CAK7dMtB3V1F=2AxtsbUznn5DO81G3Zkh9UYiN3eWkyOfV_CYmg@mail.gmail.com> <5AF1CF0F.4040909@omnilan.de> <65972f0d-2873-42ea-464c-a3db543abafb@freebsd.org> <5AF1E073.5010701@omnilan.de> <CAGK_Ob1XR_D_B=vXeHtMQwHA2yXhhWPfMtpwHKwDbGfoWgaOVw@mail.gmail.com> <5AF4875C.5000201@omnilan.de> <5AF4891A.6030904@omnilan.de> <CAGK_Ob1m34Y-b1wiqtWQhgOqrmO-XMGPL50d1K-oy=qBv_3tpQ@mail.gmail.com> <5AF48F76.4050301@omnilan.de> <CAGK_Ob3xW-UxiGm8=yEf9k048gUQ8vd86jmUiNXq2d_vPqe58g@mail.gmail.com> <5AF5D1E6.2090301@omnilan.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 11.05.2018 um 19:24 schrieb Harry Schmalzbauer: > Bezüglich Stephen Hurd's Nachricht vom 10.05.2018 21:55 (localtime): >> Ok, the review is updated with the EBR. If you can update your tree to >> r333466 or newer, apply the patch and retest, that would be great. It >> seems to be working here. > I took out the sys/net/if.c, sys/net/if_var.h and sys/conf/kmod.mk > hunks, since these were commited in r333469. > > Happy to confirm that there are no more LORs occuring when > creating/using if_lagg(4), neither with the hartwell/clarkville sisters, > nor with kawela twins. > Tested with r333486 and latest https://reviews.freebsd.org/D15355 as of > this writing. > Brief balancing/failover tests also inidcate excellent condition for > those 3 iflib-NICs. > Only did very simple workloads (with IPv6 NFSv4), but so far nothing > uncommon in any area. > Also, I cannot reproduce the link status failure when removing the TP > connection of the i217 NIC (will update the separate thread). I'd like to report additional nits with i217: While trying to track down strange symptoms (IPSec transport mode seems broken, virtualbox bridge might possibly also be broken), I saw that disabling some offload features doesn't work. ifconfig(8) doesn't report a failure, but I can't disable VLAN_HWCSUM and disablying rxcsum6 enables rxcsum4, while disabling rxcsum re-enables rxcsum6. Is it possible at all that iflib affects IPsec transport mode? Thanks, -harry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b355ffcf-a514-aaeb-7a11-39e5d437b526>