[ovs-dev] Issues with openflow protocol WAS(RE: [GIT PULL v2] Open vSwitch

[Jamal Hadi Salim]

On Mon, 2011-11-28 at 13:54 +0000, Fischer, Anna wrote:

> Yes, I mentioned this months ago, and I am surprised this critical 
> issue has never been picked up on and addressed. With a flaw like 
> this there is no chance this component can be used in any serious 
> virtualization deployment where different customers share the same physical server.
>
> The path up to user-space needs to be designed in a multi-queue fashion, so that 
> each vPort has its own queue up to user-space. Ideally those queues also need to 
> be rate controlled in some form, so that no DoS is possible.

Good - more folks scrutinizing openflow ;->
That would resolve the kernel->user if in addition you then add
prioritization of those queues. 
But even then also the same problem exists with open flow in the 
northbound direction towards the external controller where
there is a single (TCP) socket.

cheers,
jamal