https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246706
Eugene Grosbein changed:
What|Removed |Added
Resolution|--- |Overcome By Events
S
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230807
--- Comment #17 from Mark Millard ---
(In reply to Cheburashka from comment #16)
I've seen similar OS context-switching behavior with the
ThreadRipper 1950X X399 AORUS gaming 7 I use that has an
E2500. Complete power off-then-on is the onl
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230807
Cheburashka changed:
What|Removed |Added
CC||snake05...@mail.ru
--- Comment #16 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230807
--- Comment #15 from Eugene Grosbein ---
Any updates on the topic? There are reports that alc(4) is not stable for
Killer E2200 gigabit ethernet controller in 13.1
--
You are receiving this mail because:
You are on the CC list for the bug
Hi,
Some thoughts about this topic.
Delaying ACKs means loss of performance when using Gigabit TCP
connections in data centers. There it is important to ACK the data as
quick as possible, to avoid running out of TCP window space. Thinking
about TCP connections at 30 GBit/s and above!
I thin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252165
--- Comment #26 from Hans Petter Selasky ---
These issues are not forgotten. It just takes a while to find good and generic
solutions. Maybe all MII bus code should be executed for the same thread?
Would remove the need for depending on lo
