search

openvswitch / ovs-issues

Issue tracker repo for Open vSwitch
10 stars 3 forks source link

QoS Egress shaping on sending packet-in to the controller. #205

Open GraysonWu opened 3 years ago

GraysonWu commented 3 years ago

Hi there,

I want to do rate-limiting and prioritizing while sending packet-in messages to the controller. After research, I thought egress shaping met my need well. And I tried to follow the steps here: https://github.com/openvswitch/ovs/blob/80e74da4fd8bfdaba92105560ce144b4b2d00e36/Documentation/faq/qos.rst. But I didn't find how to set QoS to the controller port(65533 or 0xfffd; 0xfffffffd). Hope you guys can help me.

Thanks.

williamtu commented 3 years ago

I never tried qos on the controller. How do you setup the controller? Is it located remotely using tcp or it's local using unix domain socket? I would try adding the egress policy to the bridge itself to see if it works or not.

igsilya commented 3 years ago

@GraysonWu , since controller is not an OVS port, you can't, in general, apply QoS in a way it's applied to ports. If your controller is on a different physical machine or you know that it's behind some specific port you may apply QoS for that particular port, but I think that OF meter will be a more generic solution here. Something like that should rate-limit messages to controller to 2 packets per second: ovs-ofctl -O OpenFlow13 add-meter br0 'meter=controller pktps stats bands=type=drop rate=2' For more details see https://www.openvswitch.org/support/dist-docs/ovs-ofctl.8.html .

GraysonWu commented 3 years ago

Thank you guys for replying. It seems that OF meter works for my situation. How do you guys think about controller_queue_size, controller_rate_limit, controller_burst_limit?