On Jan 21, 2014, at 12:55 PM, Jesse Gross wrote:
> On Wed, Jan 8, 2014 at 4:15 PM, Jarno Rajahalme wrote:
>> 'perf' report on current master shows that kernel-side locking is
>> taking more than 20% of the overall OVS execution time under TCP_CRR
>> tests with flow tables that make all new conn
On Wed, Jan 8, 2014 at 4:15 PM, Jarno Rajahalme wrote:
> 'perf' report on current master shows that kernel-side locking is
> taking more than 20% of the overall OVS execution time under TCP_CRR
> tests with flow tables that make all new connections go to userspace
> and that create huge amount of
Interestingly, when running with 10 handler threads, and 4
revalidators, this doesn't seem to help much. I still see us spending
roughly 20% of the time in the kernel, and the performance benefit is
only about 2k tps. We'll need to investigate further.
Ethan
On Wed, Jan 8, 2014 at 4:15 PM, Jar
'perf' report on current master shows that kernel-side locking is
taking more than 20% of the overall OVS execution time under TCP_CRR
tests with flow tables that make all new connections go to userspace
and that create huge amount of kernel flows (~6) on a 32-CPU
server. It turns out that dis
