From nobody Fri Feb 24 06:04:59 2023 X-Original-To: net@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4PNK9m1HGJz3tKKH for ; Fri, 24 Feb 2023 06:05:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PNK9l5frRz4Z2J for ; Fri, 24 Feb 2023 06:04:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1677218699; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=uklGnHJDnWMckUCF/XALhjsCLwFTEUDoxLDTJ2Bp6lw=; b=NE3auGXHN4z4USGsr728rVNOAowupT2oOwYVccomgeq+E7ekYv03IF7Do7D17SxaCiWJDl nOiAbSFW3MvSmc1MP1ipjV/ll//Avq+8eDMJcY227gqc21GbPoYtqwyNxxZcDAGQRL9Q96 r5+qkzAs8SODbym/678WnbrlvlQLojkvxHOLU+Bi2Ne3tASdwpUsUG8Fzpao68NCpuCYgp Cuv9ey/gb2B2lcg3LlxjSUnajnX4BY1V7TBY7Y2PJUbz3oj7eIkJuKOVyJQNrFkLbNh3lh ohbAVw3MIMcg8mDZ/5XYMrLvu8O4pG4BsepZmS9a21A1hgvwq2739UaLXzOLrw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1677218699; a=rsa-sha256; cv=none; b=pmV0soZ+w23e00JQ/y+zFGS5Q3c0xXkwWNjo3/DzBdSk2Bzvt5Kg1vdGXseB4bSqTf8cLf dmei+OHcfA3gJWeII3oPcHczxgo8Ucq1aTqeP9Kb9zIuAEh2eNxLPCihu4keVyRgI4ADuz n061NnEQcqKJKwF+Cf/ICjLAAOUkd3bEVjtORMMI678MtazlGE3RUbQ906Fu/1/RimjsvK IzkjT9m5N4IKWvOpJ23Vsmsx7s/yILeDEPMZvgjUiA5+NLiaTBS8dAAUcC5oWIFn0anHGy mj1+cdxoCCIq7jA9Nk61NV+xh5OZhLewOuf7bpioN50iCx+1zJhy1H5AqRyHJw== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4PNK9l4lgRz1C4C for ; Fri, 24 Feb 2023 06:04:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 31O64xc7043985 for ; Fri, 24 Feb 2023 06:04:59 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 31O64xGV043984 for net@FreeBSD.org; Fri, 24 Feb 2023 06:04:59 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 268490] [igb] [lagg] [vlan]: Intel i210 performance severely degraded Date: Fri, 24 Feb 2023 06:04:59 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.4-RELEASE X-Bugzilla-Keywords: needs-qa, regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kbowling@freebsd.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D268490 --- Comment #29 from Kevin Bowling --- 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.=