From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jamal Hadi Salim Subject: Re: [GIT PULL v2] Open vSwitch Date: Mon, 28 Nov 2011 17:21:13 -0500 Message-ID: <1322518873.6118.7.camel@mojatatu> References: <20111123075433.GA7928@gondor.apana.org.au> <1322050976.2039.125.camel@mojatatu> <20111128130409.GB16828@gondor.apana.org.au> <1322488954.7338.66.camel@mojatatu> <20111128160117.GA6349@nicira.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: dev-yBygre7rU0TnMu66kgdUjQ@public.gmane.org, netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Herbert Xu , David Miller To: Ben Pfaff Return-path: In-Reply-To: <20111128160117.GA6349-l0M0P4e3n4LQT0dZR+AlfA@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dev-bounces-yBygre7rU0TnMu66kgdUjQ@public.gmane.org Errors-To: dev-bounces-yBygre7rU0TnMu66kgdUjQ@public.gmane.org List-Id: netdev.vger.kernel.org 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