Re: TCP Congestion Control

2019-10-28 Thread Kevin Bowling
The per socket method is used at a large commercial CDN On Thu, Oct 24, 2019 at 12:30 AM vm finance wrote: > 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! > >

Re: TCP Congestion Control

2019-10-24 Thread Tom Jones
On Wed, Oct 23, 2019 at 11:29:50PM -0700, vm finance wrote: > 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? I have not heard of any problems and have happily done recently:

Re: TCP Congestion Control

2019-10-24 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

Re: TCP Congestion Control

2019-10-24 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:

TCP Congestion Control

2019-10-24 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?

Re: Some questions about the new TCP congestion control code

2013-01-25 Thread John Baldwin
On Thursday, January 24, 2013 6:27:51 pm Lawrence Stewart wrote: On 01/25/13 01:12, Andre Oppermann wrote: On 24.01.2013 14:28, Lawrence Stewart wrote: On 01/16/13 06:27, John Baldwin wrote: One other thing I noticed which is may or may not be odd during this, is that if you have a

Re: Some questions about the new TCP congestion control code

2013-01-24 Thread Lawrence Stewart
On 01/16/13 06:27, John Baldwin wrote: On Tuesday, January 15, 2013 3:29:51 am Lawrence Stewart wrote: Hi John, On 01/15/13 08:04, John Baldwin wrote: I was looking at TCP congestion control at work recently and noticed a few Poor you ;) odd things in the current code. First

Re: Some questions about the new TCP congestion control code

2013-01-24 Thread Andre Oppermann
On 24.01.2013 14:28, Lawrence Stewart wrote: On 01/16/13 06:27, John Baldwin wrote: One other thing I noticed which is may or may not be odd during this, is that if you have a connection with TCP_NODELAY enabled and you fill your cwnd and then you get an ACK back for an earlier small segment

Re: Some questions about the new TCP congestion control code

2013-01-24 Thread Lawrence Stewart
On 01/25/13 01:12, Andre Oppermann wrote: On 24.01.2013 14:28, Lawrence Stewart wrote: On 01/16/13 06:27, John Baldwin wrote: One other thing I noticed which is may or may not be odd during this, is that if you have a connection with TCP_NODELAY enabled and you fill your cwnd and then you

Re: Some questions about the new TCP congestion control code

2013-01-15 Thread Lawrence Stewart
Hi John, On 01/15/13 08:04, John Baldwin wrote: I was looking at TCP congestion control at work recently and noticed a few Poor you ;) odd things in the current code. First, there is this chunk of code in cc_ack_received() in tcp_input.c: static void inline cc_ack_received(struct

Re: Some questions about the new TCP congestion control code

2013-01-15 Thread John Baldwin
On Tuesday, January 15, 2013 3:29:51 am Lawrence Stewart wrote: Hi John, On 01/15/13 08:04, John Baldwin wrote: I was looking at TCP congestion control at work recently and noticed a few Poor you ;) odd things in the current code. First, there is this chunk of code

Some questions about the new TCP congestion control code

2013-01-14 Thread John Baldwin
I was looking at TCP congestion control at work recently and noticed a few odd things in the current code. First, there is this chunk of code in cc_ack_received() in tcp_input.c: static void inline cc_ack_received(struct tcpcb *tp, struct tcphdr *th, uint16_t type) { INP_WLOCK_ASSERT

Modular/Pluggable TCP Congestion Control for FreeBSD

2007-12-18 Thread Lawrence Stewart
Hi all, We've been involved in a research project to implement and test an emerging TCP congestion control algorithm under FreeBSD. As a part of this, we've put together a patch for FreeBSD 7.0-BETA4 that modularises the congestion control code in the TCP stack. It allows for new congestion

Re: Modular/Pluggable TCP Congestion Control for FreeBSD

2007-12-18 Thread Andre Oppermann
Lawrence Stewart wrote: Hi all, We've been involved in a research project to implement and test an emerging TCP congestion control algorithm under FreeBSD. As a part of this, we've put together a patch for FreeBSD 7.0-BETA4 that modularises the congestion control code in the TCP stack

Re: Modular/Pluggable TCP Congestion Control for FreeBSD

2007-12-18 Thread Rui Paulo
Rui Paulo At Tue, 18 Dec 2007 13:55:20 +0100, Andre Oppermann wrote: Lawrence Stewart wrote: Hi all, We've been involved in a research project to implement and test an emerging TCP congestion control algorithm under FreeBSD. As a part of this, we've put together a patch for FreeBSD 7.0

Re: Modular/Pluggable TCP Congestion Control for FreeBSD

2007-12-18 Thread Fred Baker
Thanks to each of you. On Dec 18, 2007, at 4:55 AM, Andre Oppermann wrote: Lawrence Stewart wrote: Hi all, We've been involved in a research project to implement and test an emerging TCP congestion control algorithm under FreeBSD. As a part of this, we've put together a patch for FreeBSD 7.0