Hi Darren,
A different setsockoption for setting the received/sent MSS?
That would be a very good option.
I'm not sure that I understand what you're talking about here, can you expand on what problem you're having and how you would like to address it?
Say for example you've got a heavily utilized SMTP server. 100 different clients connect that you haven't seen before. 20 of them start transmitting 20 MB files concurrently, which completely saturates your 20 Mb/s link for 106 seconds (assuming each client is limited on their end to a T1). In this case, what I'd like to be able to do is tell the OS when the connection is built up only allow this sender to consume 100 Kb/s. If the after 3 MB they're still sending data then I'd want to ratchet them down again to probably 20 Kb/s. The reason being, these 10 senders otherwise prevent the other 80 from getting connections...or cause them to time out. Optimally, you'd just tell the OS the rate when a connection was accepted, and then have the ability to reset the rate on an ongoing connection by handing the OS Source IP/Source Port Destination, IP/Destination Port and the new rate. Then the OS would automagically adjust the MSS (on a new connection) and the TCP window to meet the set rate, since the OS is in a better position to make those decisions rapidly. Does this help? -J _______________________________________________ networking-discuss mailing list [email protected]
