Date: Mon, 16 Jul 2018 14:17:36 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 203856] [igb] PPPoE RX traffic is limitied to one queue Message-ID: <bug-203856-7501-YsUZ6A9kdz@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-203856-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-203856-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=3D203856 --- Comment #10 from ricsip <ricsip@gmail.com> --- (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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-203856-7501-YsUZ6A9kdz>