From owner-freebsd-net@freebsd.org Mon Jul 16 14:17:39 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7B7A81029C76 for ; Mon, 16 Jul 2018 14:17:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id ED6D472E5A for ; Mon, 16 Jul 2018 14:17:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id A3F3D1029C75; Mon, 16 Jul 2018 14:17:38 +0000 (UTC) Delivered-To: net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 66DE71029C72 for ; Mon, 16 Jul 2018 14:17:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F2EF872E54 for ; Mon, 16 Jul 2018 14:17:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 1258012E1B for ; Mon, 16 Jul 2018 14:17:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w6GEHaZH009341 for ; Mon, 16 Jul 2018 14:17:36 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w6GEHaX9009340 for net@FreeBSD.org; Mon, 16 Jul 2018 14:17:36 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 203856] [igb] PPPoE RX traffic is limitied to one queue Date: Mon, 16 Jul 2018 14:17:36 +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: 10.1-STABLE X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ricsip@gmail.com X-Bugzilla-Status: New 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 MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jul 2018 14:17:39 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203856 --- Comment #10 from ricsip --- (In reply to Jan Bramkamp from comment #9) Your reply greatly appreciated. My intention was to see if a stone is dropp= ed into the lake, it may create some waves and progress may happen.=20 TBH I was unaware of this issue until I faced it personally (before going i= nto prod., testbed didnt prove the expected results, and the interwebs wasnt cl= ear about this issue), and google-ing revealed many similar cases. So I had to = dig deeper into whats the current state with low-powered SOC-based firewalls running on FreeBSD. Then came the famous FreeBSD forwarding performance gui= de (https://bsdrp.net/documentation/technical_docs/performance) where I found disturbingly strange results about APU2 board, and date of that page sugges= ted this is a long known issue. Tricky situation, as there are multiple parties directly or indirectly involved: a) the SOC vendor PCENGINES, who sell (quote) "PC Engines apu boards are sm= all form factor system boards optimized for wireless routing and network securi= ty applications" --> one would assume its optimized for routing/firewalling. Warning sign for the future: if you dont see any clear, credible benchmark numbers on the vendors site! b) the software vendor: pfSense / OPNSENSE, who deliver an appliance-grade software, that supports the above SOC board --> if any bugs during use, tha= t is not clearly a HW defect (eg. overheat or faulty CPU/RAM chip), one would as= sume they can support you to fix it Then come the various "backstage" players. You dont deal with them directly, but your problem may land on their territory at the end of the day.=20 c) FreeBSD, which delivers the underlying OS. --> if the bug is not directly pfSense/OPNSENSE-level, you'd have to turn to the FreeBSD community hoping = the issue will be fixed d) the HW vendor AMD: --> if there is some performance issue, maybe its an = AMD issue --> turn to AMD for any fix e) the HW vendor Intel: --> if the issue relates to the NIC itself, its an Intel issue -->turn to Intel for any fix f) whoever else I may have forgotten --=20 You are receiving this mail because: You are the assignee for the bug.=