netdev - Re: Integration of Open vSwitch

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 30 Nov 2011 22:41:11 -0800
From:	John Fastabend <john.r.fastabend@...el.com>
To:	Eric Dumazet <eric.dumazet@...il.com>
CC:	"jhs@...atatu.com" <jhs@...atatu.com>,
	Herbert Xu <herbert@...dor.apana.org.au>,
	Jesse Gross <jesse@...ira.com>,
	netdev <netdev@...r.kernel.org>,
	"dev@...nvswitch.org" <dev@...nvswitch.org>,
	David Miller <davem@...emloft.net>,
	Stephen Hemminger <shemminger@...tta.com>,
	Chris Wright <chrisw@...hat.com>
Subject: Re: Integration of Open vSwitch

On 11/30/2011 5:21 AM, Eric Dumazet wrote:
> Le mercredi 30 novembre 2011 à 08:14 -0500, jamal a écrit :
>> On Wed, 2011-11-30 at 15:00 +0800, Herbert Xu wrote:
>>
>>
>>> The other factor I considered is scalability.  The OVS code as is
>>> is not really friendly to SMP/NUMA scalability (but as Eric pointed,
>>> neither is the classifier/action layer). 
>>
>> Did you mean the qdisc funnel-to-interface part which Eric is hopefully
>> going to work on now that bql is in? classifier/action happens way
>> before that.
> 
> Actually I am waiting for John work on this area, before wasting my
> time ;)
> 

I'll try to get these out in the next couple days. Got a few qdiscs
running without the qdisc lock today. After I get some real numbers
and make them at least a bit more presentable I'll post them so
folks can let me know if they think its the right approach.

Thanks,
John.







--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html