On Tue, 22 Feb 2005 09:42:19 -0800 Stephen Hemminger <[EMAIL PROTECTED]> wrote:
> Probably the best long term solution is to make the protocol choice > be a property of the destination cache [..] > The protocol choices are mutually exclusive, if you walk through the code > (or do experiments), you find that that only one gets used. As part of the > longer term plan, I would like to: > - have one sysctl > - choice by route and destination > - union for fields in control block I think it should be nice if we substitute in the struct tcp_opt all the structs related to the congestion control algorithms with a more generic one which could be initialized when the connection is open by reading just one sysctl which defines the algorithm to be used. This could allow later even a user-space application to set the congestion control it desires to use. > Is there interest in setting up a semi official "-tcp" tree to hold these? > because it might not be of wide interest or stability to be ready for mainline > kernel. I perfectly agree. -- Angelo Dell'Aera 'buffer' Antifork Research, Inc. http://buffer.antifork.org Metro Olografix - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
