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

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Jul 16 12:41:00 UTC 2018


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

ricsip at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ricsip at gmail.com

--- Comment #5 from ricsip at gmail.com ---
Is there any chance this defect will ever be fixed? As many Gigabit ISPs are
gaining traction worldwide, FTTH is increasing exponentially continuously, and
many providers work through PPPoE (unfortunately), that will be a huge issue
(if its not already)!

The home-built SBC routers like PCEngines APU1/2/3 series are completely
useless and simply waste of money if running Pfsense/OPNsense instead of any
Linux-based distro. Unfortunately, you cannot expect resolution from the
pfSense/OPNsense guys, if the issue is the combination of underlying Freebsd OS
+ Intel NIC driver. 

The Quad-core 1Ghz AMD CPU (or similar in such boards) becomes obviously a
bottleneck if only 1 core is forced to process the entire 1Gbit traffic, while
the other 3 cores are sitting idle 90+ % most of the time. Properly sharing the
load among the other 3 cores it would perform perfectly fine, so no real need
to buy a server-grade hardware for a firewall/router-only box that eats 20
times more electricity, and produces infinitely more noise (SBC has no FAN).

Or if you see that this issue will not be solved in the foreseeable future
(like say until 13.0), at least make this limitation visible in various places
in your manual (ex. list it as a defect in the "igb" driver manual, list it as
a defect in the MPD5 manual if using PPPoE, make note of this in the
performance/routing section of the Handbook). Pfsense/OPNsense should act
similarly, but that subject to their devs.

Thanks for your support.

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


More information about the freebsd-bugs mailing list