On Thu, May 14, 2015 at 2:17 AM, Jesse Gross wrote:
> This is basically an internal kernel optimization, so I agree with Ben
> that I would prefer not making userspace aware of this. I don't really
> think that changing the locking along the lines of what is described
> above is actually more comp
Hi Ben,
On Wed, May 13, 2015 at 1:00 AM, Ben Pfaff wrote:
> On Tue, May 12, 2015 at 10:21:19AM +0200, Duarte Nunes wrote:
>> We've observed that for high flow setup rates, the flow table becomes a
>> bottleneck since it only allows a single writer (all CRUD flow operations
>> take the ovs_mutex).
sion.
> + It should build against almost any kernel, certainly against 2.6.18
> + and later.
> +
> Q: What features are not available in the Open vSwitch kernel datapath
> that ships as part of the upstream Linux kernel?
>
> --
> 1.7.2.5
>
> ________
