Re: [ovs-dev] [PATCH 2/2] openvswitch: Optimize operations for OvS flow_stats.

2017-07-17 Thread Tonghao Zhang
> On Jul 18, 2017, at 11:14 AM, Pravin Shelar wrote: > >> >> This patch adds cpumask struct, the cpu_used_mask stores the cpu_id >> that the flow used. And we only check the flow_stats on the cpu we >> used, and it is unncessary to check all possible cpu when getting, >>

Re: [PATCH 2/2] openvswitch: Optimize operations for OvS flow_stats.

2017-07-17 Thread Pravin Shelar
On Sun, Jul 16, 2017 at 11:29 PM, Tonghao Zhang wrote: > When calling the flow_free() to free the flow, we call many times > (cpu_possible_mask, eg. 128 as default) cpumask_next(). That will > take up our CPU usage if we call the flow_free() frequently. > When we put all

[PATCH 2/2] openvswitch: Optimize operations for OvS flow_stats.

2017-07-17 Thread Tonghao Zhang
When calling the flow_free() to free the flow, we call many times (cpu_possible_mask, eg. 128 as default) cpumask_next(). That will take up our CPU usage if we call the flow_free() frequently. When we put all packets to userspace via upcall, and OvS will send them back via netlink to

[PATCH 2/2] openvswitch: Optimize operations for OvS flow_stats.

2017-07-10 Thread Tonghao Zhang
When calling the flow_free() to free the flow, we call many times (cpu_possible_mask, eg. 128 as default) cpumask_next(). That will take up our CPU usage if we call the flow_free() frequently. When we put all packets to userspace via upcall, and OvS will send them back via netlink to