You'd want to enhance netdev_get_queue() to support these properties, and then push that down to every netdev implementation via netdev_class.
On Sat, May 07, 2016 at 12:05:49PM +0000, fatt 3issam wrote: > It's obvious that it's hard coded. The correct values should be read > from the actual queue configuration not typed by hand!the comment said > they omitted min and max rate. why? I can't understand even if it's so > clear to some of you!OVS doesn't advertise the "other-config" / > properties of a queue so OpenFlow can't really read them!So I'm trying > to code something that makes OpenFlow read them and I don't know where > to start so if you please tell me where can I get those properties > (code wise) so I can implement them!! > > > Date: Fri, 6 May 2016 08:09:00 -0700 > > From: b...@ovn.org > > To: fat...@hotmail.com > > CC: discuss@openvswitch.org > > Subject: Re: [ovs-discuss] queue_get_config_reply issue > > > > On Fri, May 06, 2016 at 09:14:53AM +0000, fatt 3issam wrote: > > > Could you please tell me what this means in ofproto/ofproto.c in the > > > method put_get_config_reply(...) > > > (https://github.com/openvswitch/ovs/blob/master/ofproto/ofproto.c#L6271) > > > : > > > /* None of the existing queues have compatible properties, so we hard-code > > > * omitting min_rate and max_rate. */ > > > > It seems pretty clear to me, what question do you have about it? > > > > > and how may I code min and max rates to read the actual configured > > > queues properties? > > > > Fill in the correct values, I guess. > _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
