On Tuesday, February 05, 2013 12:44:27 pm Andre Oppermann wrote: > On 05.02.2013 18:11, John Baldwin wrote: > > On Wednesday, January 30, 2013 12:26:17 pm Andre Oppermann wrote: > >> You can simply create your own congestion control algorithm with only the > >> restart window changed. See (pseudo) code below. BTW, I just noticed that > >> the other cc algos don't do not reset the idle window. > > > > *sigh* I am fully competent at maintaining my own local changes. The point > > was to share this so that other people with similar workloads could make use > > of it. Also, a custom CC algo is not the right approach as we would want > > this > > change regardless of the CC algo used for handling non-idle periods (so that > > this is an orthogonal knob). Linux also makes this an orthogonal knob > > rather > > than requiring a separate CC algo. > > If everything Linux does is good, then go ahead and commit it. Discussing > this change further then is pointless. I don't mind too much and I have > stated my case why I think it's the wrong thing to do.
Not everything Linux does is good, nor is everything Linux does bad. > I would prefer to encapsulate it into its own > not-so-much-congestion-management > algorithm so you can eventually do other tweaks as well like more aggressive > loss recovery which would fit your objective as well. Since you have to > modify > your app anyways to do the sockopt call this seems a more complete solution to > me. At least better than to do a non-portable hack that violates one of the > most fundamental TCP concepts. This is real rich from the guy pushing the increased IW that came from Linux. :) "Tools not policy" yadda yadda, but I digress. -- John Baldwin _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
