Originally posted by: jklotz
I don't have an answer to the question (I'd like to), but being able to limit network bandwith is a very valid point.
First, a similar tool exist for disk bandwith (workload manager).
Second, you never know how a system can go wrong (bug or bad user action), so it's realistic to encounter some scenarios where a partition could outbound so much traffic network that other actual critical partitions (think of a database partition used by SAP for example) could suffer from network bandith degradation.
A way to control a bit the network trafic would be NOT to optimize the IP stack of a partition (which means that if you need to give it a network boost, you have to interrupt the network stack for several minutes).
For example, I have a case (specific to my environment, so may or may not be reproduced in yours to the same scale) where a partition can have a 90/100 MB/s data rate with standard IP parameters (mtu=1500 and mtu_bypass left to off), and can reach 450 MB/s when communicating with another partition located on a second physical server, with a mtu of 9000 and the mtu_bypass set to on).