On Thu, Mar 05, 2015 at 12:22:12PM +0000, Rui Braz wrote: > Hello. I'm trying to implement some kind of qos by limiting the rate of a > port using queues. > > > The topology is the following: > > h1-eth0<->s1-eth1 > s1-eth2<->s2-eth1 > s2-eth2<->h2-eth0 > > > s1-eth1 is ofport=1 > > s1-eth2 is ofport=2 > > s2-eth1 is ofport=1 > > s2-eth2 is ofport=2 > > > The links speed is 100mb, I'm using openflow1.0 (also tried 1.3 version) and > openvswitch 2.3 (also tried 2.0.2 version). > > > So far I've created the 2 qos rows, one on port s1-eth2 and other on s2-eth1. > On both those ports I've created a queue with id=1 with max rate=20000 and > min rate=5000. This was done using this commands : > > sudo ovs-vsctl -- set port s1-eth2 qos=@newqos -- --id=@newqos create qos > type=linux-htb other-config:max-rate=10000000 queues:1=@newQ -- --id=@newQ > create queue other-config:min-rate=5000 other-config:max-rate=20000 > > > sudo ovs-vsctl -- set port s2-eth1 qos=@newqos -- --id=@newqos create qos > type=linux-htb other-config:max-rate=10000000 queues:1=@newQ -- --id=@newQ > create queue other-config:min-rate=5000 other-config:max-rate=20000 > > > After that I added 4 flows in order to H1 and H2 communicate through that > queues: > > > sudo ovs-ofctl add-flow s2 > priority=50,dl_type=0x0800,nw_src=10.0.0.2,nw_dst=10.0.0.1,actions=enqueue:1:1 > sudo ovs-ofctl add-flow s2 > priority=50,dl_type=0x0800,nw_src=10.0.0.1,nw_dst=10.0.0.2,actions=output:2 > sudo ovs-ofctl add-flow s1 > priority=50,dl_type=0x0800,nw_src=10.0.0.1,nw_dst=10.0.0.2,actions=enqueue:2:1 > sudo ovs-ofctl add-flow s1 > priority=50,dl_type=0x0800,nw_src=10.0.0.2,nw_dst=10.0.0.1,actions=output:1 > > The hosts can now communicate however by doing iperf the result is around > 90mb instead of being around 20mb > Also if after that I run the command ovs-ofctl queue-stats s1 the result is: > OFPST_QUEUE reply (xid=0x2): 0 queues > > What is the problem that causes this kind of behaviour? I've added the queues > and I can see them on the table Queue as well as I can see the Qos rows on > the table Qos.
The first thing to do is to check the ovs-vswitchd log. Likely, there was a problem configuring the queues. _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
