From mboxrd@z Thu Jan 1 00:00:00 1970 From: jamal Subject: Re: Integration of Open vSwitch Date: Wed, 30 Nov 2011 09:01:55 -0500 Message-ID: <1322661715.2243.33.camel@mojatatu> References: <20111130070011.GA32630@gondor.apana.org.au> <1322658891.2243.15.camel@mojatatu> <20111130134028.GA3226@gondor.apana.org.au> Reply-To: jhs-jkUAjuhPggJWk0Htik3J/w@public.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: dev-yBygre7rU0TnMu66kgdUjQ@public.gmane.org, Chris Wright , Eric Dumazet , netdev , John Fastabend , Stephen Hemminger , David Miller To: Herbert Xu Return-path: In-Reply-To: <20111130134028.GA3226-lOAM2aK0SrRLBo1qDEOMRrpzq4S04n8Q@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 Wed, 2011-11-30 at 21:40 +0800, Herbert Xu wrote: > I actually meant the scalability with adding/deleting flows, > or in the case with qdiscs, filters. Ah yes, them locks. Unless you start doing per-cpu tables with lazy synchronization i am not sure how to avoid that. Note: last time (time flies) i compared against iptables, the tc flow setup/teardown was pretty consistent regardless of table size relatively speaking. cheers, jamal