On Mon, 2011-11-28 at 08:01 -0800, Ben Pfaff wrote: > Regarding OpenFlow rate limiting, in addition to Martin's response, Open > vSwitch has implemented controller rate limiting since day one. It is > documented in ovs-vswitchd.conf.db(5):
Ok, I think thats a good start. My experience says just rate limiting may not be sufficient - unless the rate limiting is adaptive in some form; or just use strict prio where you let the exception traffic rot if you have other work - maybe thats what Martin was talking about. The problem is more in the outbound towards the external controller. You dont have multiple queues (given a single TCP socket) and config, events, and exception packets are all shared in one queue. cheers, jamal _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
