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? Thanks! Haleema On Sat, May 2, 2015 at 10:25 PM, Ben Pfaff <[email protected]> wrote: > It looks like mininet is taking charge of the qdisc on s1-eth1. There > can only be one configuration, so if mininet wants to set it one way and > OVS the other then only one can win. I suspect you should talk to the > mininet folks. > > On Sat, May 02, 2015 at 10:17:19AM -0700, Haleema Sadia wrote: > > Here it is! > > > > On Sat, May 2, 2015 at 10:16 AM, Ben Pfaff <[email protected]> wrote: > > > > > Can you provide the ovs-vswitchd log? > > > > > > On Sat, May 02, 2015 at 09:58:34AM -0700, Haleema Sadia wrote: > > > > My mininet wasn't working before when I type the command, but I > restarted > > > > it and now the command shows this: > > > > > > > > qdisc pfifo_fast 0: dev eth0 root refcnt 2 bands 3 priomap 1 2 2 2 > 1 2 > > > 0 0 > > > > 1 1 1 1 1 1 1 1 > > > > qdisc htb 5: dev s1-eth1 root refcnt 2 r2q 10 default 1 > > > direct_packets_stat > > > > 0 direct_qlen 1000 > > > > qdisc netem 10: dev s1-eth1 parent 5:1 limit 1000 delay 99us > > > > qdisc htb 5: dev s1-eth2 root refcnt 2 r2q 10 default 1 > > > direct_packets_stat > > > > 0 direct_qlen 1000 > > > > qdisc netem 10: dev s1-eth2 parent 5:1 limit 1000 delay 99us > > > > qdisc htb 5: dev s1-eth3 root refcnt 2 r2q 10 default 1 > > > direct_packets_stat > > > > 0 direct_qlen 1000 > > > > qdisc netem 10: dev s1-eth3 parent 5:1 limit 1000 delay 99us > > > > > > > > (the topology is one switch and three hosts) > > > > > > > > And I am attaching my kern.log > > > > > > > > > > > > > > > > On Sat, May 2, 2015 at 9:33 AM, Ben Pfaff <[email protected]> wrote: > > > > > > > > > OK, the linux-htb qdisc isn't really getting configured. We'll > have to > > > > > figure out why. > > > > > > > > > > Is the htb kernel module loaded? Is there anything in the kernel > log > > > > > related to htb? > > > > > > > > > > On Sat, May 02, 2015 at 09:20:19AM -0700, Haleema Sadia wrote: > > > > > > It says: > > > > > > > > > > > > qdisc pfifo_fast 0: dev eth0 root refcnt 2 bands 3 priomap 1 2 > 2 2 > > > 1 2 > > > > > 0 0 > > > > > > 1 1 1 1 1 1 1 1 > > > > > > > > > > > > > > > > > > On Sat, May 2, 2015 at 9:17 AM, Ben Pfaff <[email protected]> > wrote: > > > > > > > > > > > > > Check whether the kernel shows the qdisc being configured: "tc > > > qdisc > > > > > > > show". > > > > > > > > > > > > > > On Sat, May 02, 2015 at 05:11:30PM +0500, Haleema Sadia wrote: > > > > > > > > Hi Ben, > > > > > > > > > > > > > > > > Thanks for your response! > > > > > > > > > > > > > > > > The ovs-vswitchd log shows shows no error and neither does it > > > says > > > > > > > anything > > > > > > > > about the queue creation. Is that fine? However, I do get the > > > qos id > > > > > and > > > > > > > > the queue id when I create them. > > > > > > > > > > > > > > > > On Sat, May 2, 2015 at 3:57 AM, Ben Pfaff <[email protected]> > > > wrote: > > > > > > > > > > > > > > > > > On Thu, Apr 30, 2015 at 11:52:45AM +0500, Haleema Sadia > Mahmood > > > > > wrote: > > > > > > > > > > So I am trying to configure queues on a mininet > topology. The > > > > > command > > > > > > > > > that I use is, (here s1-eth1 is my port 1) > > > > > > > > > > > > > > > > > > > > sudo ovs-vsctl set port s1-eth1 qos=@newqos - - - > > > -id=@newqos > > > > > create > > > > > > > > > qos type=linux-htb queues=0=@q0 - - - -id=@q0 create > queue > > > > > > > > > other-config:max-rate=100000000 > other-config:min-rate=5000000 > > > - - > > > > > > > > > > > > > > > > > > > > The qos is attached to the port, checked it from sudo > > > ovs-vsctl > > > > > list > > > > > > > > > port s1-eth1, and the queues are created. > > > > > > > > > > > > > > > > > > Probably the queues aren't really created. Check the > > > ovs-vswitchd > > > > > log > > > > > > > > > for error messages. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
