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]

Message-ID: <CAEP_g=9B-5LT=bm45s9yQzEK-YFB1QWVpHxHpnLdQ+W2BZDf1g@mail.gmail.com>
Date:	Fri, 2 Dec 2011 15:08:08 -0800
From:	Jesse Gross <jesse@...ira.com>
To:	Herbert Xu <herbert@...dor.apana.org.au>
Cc:	jhs@...atatu.com, netdev <netdev@...r.kernel.org>,
	dev@...nvswitch.org, David Miller <davem@...emloft.net>,
	Stephen Hemminger <shemminger@...tta.com>,
	Chris Wright <chrisw@...hat.com>,
	John Fastabend <john.r.fastabend@...el.com>,
	Eric Dumazet <eric.dumazet@...il.com>
Subject: Re: Integration of Open vSwitch

On Tue, Nov 29, 2011 at 11:00 PM, Herbert Xu
<herbert@...dor.apana.org.au> 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).  However, if this were to
> become a problem in future I'm sure we could extend either the
> interface as is (e.g., deploying multiqueue netlink sockets), or
> migrate to something else.

I agree that adding new flows is a weakness of the OVS model
(obviously it was a trade off) that has some room to be improved.
But, as you say, that's more of a long-term project that I think can
be done incrementally over time.

> So I don't really have any objections to this going into the tree.

Great, thanks for reviewing.
--
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