https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276890
--- Comment #5 from Dave Taht ---
I am a little dubious about the "active" idea.
http://fxr.watson.org/fxr/source/netpfil/ipfw/dn_sched_fq_codel.c#L413
Also.
if (!si->flows[idx].active ) {
319
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276890
--- Comment #4 from Dave Taht ---
Assuming I am looking at a correct source tree:
http://fxr.watson.org/fxr/source/netpfil/ipfw/dn_sched_fq_codel.c#L330
Logging an overflow event twice, and to the console, while under stress, is not
a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276890
--- Comment #3 from Dave Taht ---
One of the issues with the freebsd implementation appears to be too much
logging:
https://forum.opnsense.org/index.php?topic=39046.0
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276890
--- Comment #2 from Dave Taht ---
I got some packet captures from an opnsense user, who also on my behalf turned
on and off LRO. One of the test runs was decidedly odd in that it missed the
target for far, far too long, which could be just
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276890
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276890
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are
