Re: Selection of TCP congestion avoidance algo per interface?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 22 Sep 2005, Dag Bakke wrote:

This requires the proxy to make this decision for every in- and out-bound connection, right? (I am firmly peeking over the edge of my knowledge here, staring into the great void.)

Probably.

On the the "listening" side it may work to set it on the listen socket, but probably not..

Hope I manage to spur a discussion around this, as I don't code myself...

Having the decision made by routing similar to how MSS & window sizes etc can be decided surely makes most sense, but I would not bet that someone finds this sufficiently interesting to implement it out of the void for you.

But it should not be much more than adding a new value to RTM_METRICS, and a dst_metrics() lookup at the appropriate place plus additions to iproute to allow the value to be sent to the kernel, but there is complications in that the current RTM_METRICS is all based arount integers while the congestion control algorithms is all named by strings. But on the other hand this probably should be changed for efficiency anyway if doing this as doing a string based lookup for the congestion control algorithm on each new tcp connection is probably not wanted.

Regards
Henrik
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux