[ovs-discuss] Is there a plan on extracting upcall handling work from ovs-vswitchd process as a single thread?

[jerry]

Justin,

Thanks very much for your reply.

I'm not sure that how you to make ovs-vswitchd multithreaded.

What is the train of thought on the work to make ovs-vswitchd multithreaded?   Could you share some thinking with me?

Best Regards,
Jerry
>
>
> -----邮件原件-----
> 发件人: Justin Pettit [mailto:jpettit at nicira.com]
> 发送时间: 2013年6月5日 23:25
> 收件人: Lilijun (Jerry)
> 抄送: discuss at openvswitch.org; Zhbzg
> 主题: Re: [ovs-discuss] Is there a plan on extracting upcall handling work from ovs-vswitchd process as a single thread?
>
> (The original request got stuck in a mailman queue, so it just not got reposted.  For anybody that didn't see the response over the weekend, here it is again.)
>
> There is work underway to make ovs-vswitchd multithreaded.
>
> --Justin
>
>
> On Jun 4, 2013, at 4:04 AM, Lilijun (Jerry) <jerry.lilijun at huawei.com> wrote:
>
>> Hi, all,
>> In my test, when many different ARP request traffics are received from outline, OVS’s kernel module will do upcall for these packets in order to find openflow rules.
>> Then ovs-vswitchd process will handle each packet and it’s CPU cost may reach up to 100%, at a result, other control commands will be blocked and can’t be handled.
>> So can we extract upcall handling work from ovs-vswitchd process as a single thread? Is there such plan for resolving this problems?
>>
>> Thanks,
>> Jerry
>> _______________________________________________
>> discuss mailing list
>> discuss at openvswitch.org
>> http://openvswitch.org/mailman/listinfo/discuss
>