netdev - Re: [ovs-dev] [GIT PULL v2] 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: <1322494356.7338.75.camel@mojatatu>
Date:	Mon, 28 Nov 2011 10:32:36 -0500
From:	Jamal Hadi Salim <jhs@...atatu.com>
To:	Martin Casado <casado@...ira.com>
Cc:	Herbert Xu <herbert@...dor.apana.org.au>, dev@...nvswitch.org,
	netdev@...r.kernel.org, David Miller <davem@...emloft.net>
Subject: Re: [ovs-dev] [GIT PULL v2] Open vSwitch

On Mon, 2011-11-28 at 07:27 -0800, Martin Casado wrote:

> This is a common misunderstanding about OpenFlow.  It does not require 
> the first packet of each flow to go to the controller.  

I am reading this to mean that the switch CPU will resolve things?
Typically those tend to be tiny cpus.

> In fact, no 
> production system I'm aware of does this.  Generally OpenFlow-based 
> solutions targeted at large environments (e.g. data center, or WAN)  
> send only traditional control traffic to the controller (e.g. BGP or 
> OSPF), or none at all.

Even OSPF or BGP  would be problematic imo if the architecture doesnt
allow prioritization of some form towards the controller.

cheers,
jamal


--
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