[ovs-discuss] Two ovs-vswitchd threads
Kmindg G
kmindg at gmail.com
Mon Jul 21 09:00:55 UTC 2014
On Mon, Jul 21, 2014 at 4:55 PM, Kmindg G <kmindg at gmail.com> wrote:
> Hi,
> When I set-controller to ovs in sandbox, I find that there're two
> ovs-vswitchd threads.
>
>
> ps -L -p 19336
> PID LWP TTY TIME CMD
> 19336 19336 ? 00:00:00 ovs-vswitchd
> 19336 19368 ? 00:00:00 handler1
> 19336 19369 ? 00:00:00 revalidator2
> 19336 19370 ? 00:00:00 urcu3
>
> ovs-vsctl set-controller br0 tcp:3.3.3.3
>
> ps -L -p 19336
>
> PID LWP TTY TIME CMD
> 19336 19336 ? 00:00:00 ovs-vswitchd
> 19336 19370 ? 00:00:00 urcu3
> 19336 19615 ? 00:00:00 handler5
> 19336 19616 ? 00:00:00 revalidator4
> 19336 19627 ? 00:00:00 ovs-vswitchd
>
> ps -L -p 19336
> PID LWP TTY TIME CMD
> 19336 19336 ? 00:00:00 ovs-vswitchd
> 19336 19370 ? 00:00:00 urcu3
> 19336 19615 ? 00:00:00 handler5
> 19336 19616 ? 00:00:00 revalidator4
> 19336 19712 ? 00:00:00 ovs-vswitchd
>
> 1. I don't change n_handler_thread or n_revalidator_thread, but handler
> and revalidator threads change.
> 2. thread id of the second ovs-vswitchd changes all the time.
> Is this the expected behavior?
>
> Thanks
> Kmindg
>
Forget to mention that I test with commit db73f71(netdev-dpdk: Fix race
condition with DPDK mempools in non pmd threads) on master branch.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20140721/990077e4/attachment-0002.html>
More information about the discuss
mailing list