[ovs-discuss] ovs-ofctl queue-get-config issue

fatt 3issam fatt_8 at hotmail.com
Tue May 3 20:04:38 UTC 2016

Thanks for the instant reply.All that mininet can do is to fix somewhat link bandwidth with the tc tool but the ports of ovs would still advertise the same original speed because they are virtual! I actually need that actual port speed to be limited to say 2MB instead of 10GB for example or at least have a default queue of that 2MB as a work around. So in the end I need to get either the port speed (which is of course constant and inherited from the physical eth interface and all ovs can do is to read it) or the queue rate (which you said it's an OpenFlow incomplete feature!), it needs to be read by OpenFlow necessarily because it's the only way a controller could request an openflow vswitch. I guess I can get with forwarding flows on a certain limit but I could never know the actual bandwidth utilization on a port because the port's speed is a constant that depends on my machine!

> Date: Tue, 3 May 2016 12:36:11 -0700
> From: blp at ovn.org
> To: fatt_8 at hotmail.com
> CC: discuss at openvswitch.org
> Subject: Re: [ovs-discuss] ovs-ofctl queue-get-config issue
> I don't think that HTB works on a virtual interface anyhow; I believe
> that it needs a fixed link speed.
> I think that mininet can do what you want, so you might want to ask on a
> mininet mailing list.
> On Tue, May 03, 2016 at 07:29:58PM +0000, fatt 3issam wrote:
> > Thank you.If I understood, No version of OpenFlow can tell me max and min rates of a queue on an OVS and I totally can't force a link-rate  nor a port speed by any means in OVS because they are virtual interfaces. What should I do then to limit the bandwidth in a simulated network of Open VSwitches?!
> > > Date: Tue, 3 May 2016 10:12:54 -0700
> > > From: blp at ovn.org
> > > To: fatt_8 at hotmail.com
> > > CC: discuss at openvswitch.org
> > > Subject: Re: [ovs-discuss] ovs-ofctl queue-get-config issue
> > > 
> > > On Tue, May 03, 2016 at 11:38:49AM +0000, fatt 3issam wrote:
> > > > When executing the command: # ovs-ofctl queue-get-config swicth switch-port, i only get the queue id!! 
> > > > OFPT_QUEUE_GET_CONFIG_REPLY (OF1.3) (xid=0x4): port=2queue 0:
> > > > I want to get the queue properties also!
> > > > my queue configuration is: # ovs-vsctl set port switch-port qos=@newqos -- --id=@newqos create qos type=linux-htb other-config:max-rate=20000000 queues:0=@newqueue -- --id=@newqueue create queue other-config:min-rate=1000000 other-config:max-rate=1000000
> > > > Does anyone know what's the problem here? I also checked wireshark for OFPT_QUEUE_GET_CONFIG_REPLY packets and it doesn't give any properties too (only the queue id, the port, length and pad) although it should give them based on OpenFlow specifications.
> > > > I'm I doing something wrong?
> > > 
> > > OpenFlow doesn't define min-rate and max-rate in a way compatible with
> > > Open vSwitch: it wants them as a percentage of the line rate, whereas
> > > Linux specifies them in absolute terms.  No one has written code to do
> > > the conversion yet.
> >  		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20160503/2bd1dd18/attachment-0002.html>

More information about the discuss mailing list