Re: TCP Congestion Control

2019-10-23 Thread vm finance
Ok - I see there is a socket option to pick a different cc per-socket basis. Any experiences on loading / using different cc per socket...does it work seamlessly? Thanks! On Wed, Oct 23, 2019 at 11:19 PM Kevin Oberman wrote: > Have you loaded kernel modules for other algorithms? I believe only

Re: TCP Congestion Control

2019-10-23 Thread Kevin Oberman
Have you loaded kernel modules for other algorithms? I believe only newreno is in the default kernel. "man 4 mod_cc" for available modules and other information. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B3

TCP Congestion Control

2019-10-23 Thread vm finance
Hi, We can set per-socket congestion control under Linux, but not under FreeBSD (12.0). The current available and allowed is only newReno: net.inet.tcp.cc.available: newreno net.inet.tcp.cc.algorithm: newreno Any thoughts on why FreeBSD chose not to allow different cc to be set per socket? AFAIK,

[Bug 235524] igb ethernet interface loses active link state

2019-10-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235524 --- Comment #2 from Denis Ahrens --- it seems that r353778 - head/sys/dev/e1000 fixed my problem. running now for 36h without a problem will close this as fixed in a week denis -- You are receiving this mail because: You are the assign

Re: Still em(4) broken with epoch changes

2019-10-23 Thread Konstantin Belousov
On Wed, Oct 23, 2019 at 09:39:36AM +0200, Hans Petter Selasky wrote: > On 2019-10-23 09:33, Konstantin Belousov wrote: > > I tried to netboot my test box today with r353914 kernel, and still I get > > the following panic on machine attempt to start multiuser: > > > > Feeding entropy: . > > lo0: li

Re: Still em(4) broken with epoch changes

2019-10-23 Thread Hans Petter Selasky
On 2019-10-23 09:33, Konstantin Belousov wrote: I tried to netboot my test box today with r353914 kernel, and still I get the following panic on machine attempt to start multiuser: Feeding entropy: . lo0: link state changed to UP uhub0: 3 ports with 3 removable, self powered uhub1: 3 ports with

Still em(4) broken with epoch changes

2019-10-23 Thread Konstantin Belousov
I tried to netboot my test box today with r353914 kernel, and still I get the following panic on machine attempt to start multiuser: Feeding entropy: . lo0: link state changed to UP uhub0: 3 ports with 3 removable, self powered uhub1: 3 ports with 3 removable, self powered panic: sleeping in an ep