Date: Fri, 24 Feb 2023 06:04:59 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 268490] [igb] [lagg] [vlan]: Intel i210 performance severely degraded Message-ID: <bug-268490-7501-iVmpR8J5BZ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-268490-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-268490-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D268490 --- Comment #29 from Kevin Bowling <kbowling@freebsd.org> --- I think the intention there is to try and figure out what coincidental comm= it could be at fault because the offending commit is just enabling functionali= ty but is not necessarily a smoking gun. I'm not sure if there is a streamlin= ed way to do this kind of bisect, hopefully 'git cherry-pick' and 'git reset' = will suffice in the build/test loop. Right now the likely suspects could be flag management changes in e1000 or = some change in lagg(4) I am not privy to. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-268490-7501-iVmpR8J5BZ>