I agree with the OVS FAQ entry, and I will add one comment: For now, you should configure tc/QoS using either Mininet *or* OVS, but not both; if you try to use both of them on the same interface, one will overwrite the other. Probably you want to use ovs-vsctl for OVS data ports, and Mininet’s TCIntf for others.
Andrew Ferguson submitted a pull request to both mechanisms to coexist, but this has not been merged into the mainline code base. > On May 4, 2015, at 9:39 AM, Ben Pfaff <[email protected]> wrote: > > On Mon, May 04, 2015 at 05:22:24PM +0500, Haleema Sadia wrote: >> The issue is resolved now.. I was setting up the bandwidth and delay >> variable in the mininet custom topology that I created. Once I removed them >> the queues starting working. However, if I have different min/max rate for >> the queues the min rate threshold is not maintained. >> >> For ex, if min-rate is 4 Megabit and I specify the udp packet rate to be 3 >> Megabit, the bandwidth on the server side(where the queue is being >> maintained) for iperf goes to 3 Megabit. >> >> Do you have any idea why? > > It's hard for me to understand exactly what you're asking, but this FAQ > might help. > > ### Q: I configured QoS, correctly, but my measurements show that it isn't > working as well as I expect. > > A: With the Linux kernel, the Open vSwitch implementation of QoS has > two aspects: > > - Open vSwitch configures a subset of Linux kernel QoS > features, according to what is in OVSDB. It is possible that > this code has bugs. If you believe that this is so, then you > can configure the Linux traffic control (QoS) stack directly > with the "tc" program. If you get better results that way, > you can send a detailed bug report to [email protected]. > > It is certain that Open vSwitch cannot configure every Linux > kernel QoS feature. If you need some feature that OVS cannot > configure, then you can also use "tc" directly (or add that > feature to OVS). > > - The Open vSwitch implementation of OpenFlow allows flows to > be directed to particular queues. This is pretty simple and > unlikely to have serious bugs at this point. > > However, most problems with QoS on Linux are not bugs in Open > vSwitch at all. They tend to be either configuration errors > (please see the earlier questions in this section) or issues with > the traffic control (QoS) stack in Linux. The Open vSwitch > developers are not experts on Linux traffic control. We suggest > that, if you believe you are encountering a problem with Linux > traffic control, that you consult the tc manpages (e.g. tc(8), > tc-htb(8), tc-hfsc(8)), web resources (e.g. http://lartc.org/), or > mailing lists (e.g. http://vger.kernel.org/vger-lists.html#netdev). > _______________________________________________ > discuss mailing list > [email protected] > http://openvswitch.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
