Date: Wed, 23 Oct 2019 23:19:42 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: vm finance <vm.finance2@gmail.com> Cc: freebsd-net <freebsd-net@freebsd.org> Subject: Re: TCP Congestion Control Message-ID: <CAN6yY1tCbpuGrwqNkHAiH2MNwQjSpxZfFJZxoARZCYkgURgQvg@mail.gmail.com> In-Reply-To: <CAKy-8=jcS33K_7otwHrRF2miWvn--adCBSLR8s8yQ1TA21oF-g@mail.gmail.com> References: <CAKy-8=jcS33K_7otwHrRF2miWvn--adCBSLR8s8yQ1TA21oF-g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Wed, Oct 23, 2019 at 11:04 PM vm finance <vm.finance2@gmail.com> wrote: > 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, it would get complicated to have different sessions having different > congestion algos. > > Thanks for any pointers! > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1tCbpuGrwqNkHAiH2MNwQjSpxZfFJZxoARZCYkgURgQvg>