[Bug 203856] [igb] PPPoE RX traffic is limitied to one queue

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Jul 16 14:17:39 UTC 2018


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203856

--- Comment #10 from ricsip <ricsip at gmail.com> ---
(In reply to Jan Bramkamp from comment #9)

Your reply greatly appreciated. My intention was to see if a stone is dropped
into the lake, it may create some waves and progress may happen. 

TBH I was unaware of this issue until I faced it personally (before going into
prod., testbed didnt prove the expected results, and the interwebs wasnt clear
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 guide
(https://bsdrp.net/documentation/technical_docs/performance) where I found
disturbingly strange results about APU2 board, and date of that page suggested
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 small
form factor system boards optimized for wireless routing and network security
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, that is
not clearly a HW defect (eg. overheat or faulty CPU/RAM chip), one would assume
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. 

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

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-net mailing list