On Wed, Aug 13, 2014 at 09:58:09PM +0530, Monica Gawas wrote: > Ben Flaff : "What do you see as the most important deficiency?" > > Being quite the beginners in this stuff, we found some very basic > deficiencies like : > 1. QoS implementations in ovs only support a simple rate limiting , > rather than intelligent QoS with a minimum bandwidth > guarantee. With rate limiting, each queue is assigned a specific > amount of bandwidth that cannot be exceeded. But what if > the queue is being under-utilized ? > 2. Uncontrolled incoming traffic at the device, to a VM that is sharing a > network device, can severely impact the performance of > other VMs because the decision to drop an incoming packet is taken > after the device has received the packet. This could > potentially cause a denial of service attack on the VMs sharing the > device.
OVS (on Linux) uses Linux kernel provided QoS. It sounds like you want to develop new Linux queuing disciplines. That's nice, but it's not really OVS development--the only code you'd need in OVS is code to configure the kernel support for whatever queuing discipline you build. _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
