Re: [ovs-dev] [ovs dpdk] why all the ovs threads pinned to master lcore?

2016-10-25 Thread Kevin Traynor
Christian Ehrhardt <christian.ehrha...@canonical.com>; ychen >> <ychen103...@163.com>; dev@openvswitch.org >> Subject: Re: [ovs-dev] [ovs dpdk] why all the ovs threads pinned to master >> lcore? >> >> "Bodireddy, Bhanuprakash" <bhanuprakash.bodire...@in

Re: [ovs-dev] [ovs dpdk] why all the ovs threads pinned to master lcore?

2016-10-25 Thread Bodireddy, Bhanuprakash
...@163.com>; dev@openvswitch.org >Subject: Re: [ovs-dev] [ovs dpdk] why all the ovs threads pinned to master >lcore? > >"Bodireddy, Bhanuprakash" <bhanuprakash.bodire...@intel.com> writes: > >>> >>>++ pidof ovs-vswitchd >>>+ ps -To tid,pid,psr,c

Re: [ovs-dev] [ovs dpdk] why all the ovs threads pinned to master lcore?

2016-10-25 Thread Aaron Conole
"Bodireddy, Bhanuprakash" writes: >> >>++ pidof ovs-vswitchd >>+ ps -To tid,pid,psr,comm -p 25932 >> TID PID PSR COMMAND >>25932 25932 1 ovs-vswitchd >>25934 25932 0 eal-intr-thread >>25935 25932 1 dpdk_watchdog1 >>25936 25932 2 vhost_thread2 >>25937

Re: [ovs-dev] [ovs dpdk] why all the ovs threads pinned to master lcore?

2016-10-25 Thread Bodireddy, Bhanuprakash
> >sorry, I am still confused. >when I launched vswitchd with dpdk-init=false, all the threads changed their >pinned cores as time goes by. >The following output is from ovs version 2.6 with dpdk-init=false ps -To >tid,pid,psr,comm -p 5922 > TIDPID PSR COMMAND > 5922 5922 12 ovs-vswitchd

Re: [ovs-dev] [ovs dpdk] why all the ovs threads pinned to master lcore?

2016-10-25 Thread Bodireddy, Bhanuprakash
> >++ pidof ovs-vswitchd >+ ps -To tid,pid,psr,comm -p 25932 > TID PID PSR COMMAND >25932 25932 1 ovs-vswitchd >25934 25932 0 eal-intr-thread >25935 25932 1 dpdk_watchdog1 >25936 25932 2 vhost_thread2 >25937 25932 1 pdump-thread >25938 25932 8 urcu3 >25939 25932 2 ovs-vswitchd

Re: [ovs-dev] [ovs dpdk] why all the ovs threads pinned to master lcore?

2016-10-25 Thread Christian Ehrhardt
On Tue, Oct 25, 2016 at 4:08 AM, ychen wrote: > When launch vswitchd with dpdk-init as true, all the handler threads and > revalidator threads are pinned to master lcore and can not change their > pinned cores when time goes by. > so here is my problem: > 1. with the same

Re: [ovs-dev] [ovs dpdk] why all the ovs threads pinned to master lcore?

2016-10-24 Thread ychen
sorry, I am still confused. when I launched vswitchd with dpdk-init=false, all the threads changed their pinned cores as time goes by. The following output is from ovs version 2.6 with dpdk-init=false ps -To tid,pid,psr,comm -p 5922 TIDPID PSR COMMAND 5922 5922 12 ovs-vswitchd 5934

Re: [ovs-dev] [ovs dpdk] why all the ovs threads pinned to master lcore?

2016-10-24 Thread Kevin Traynor
On 10/24/2016 11:55 AM, ychen wrote: > hi, I am a freshman to ovs DPDK, when I tried to launch ovs with dpdk inited, > I found that all the ovs threads are pinned to master lcore, > but I can't find any code for setting the affinity of the specified thread. On older versions of OVS you you can

[ovs-dev] [ovs dpdk] why all the ovs threads pinned to master lcore?

2016-10-24 Thread ychen
hi, I am a freshman to ovs DPDK, when I tried to launch ovs with dpdk inited, I found that all the ovs threads are pinned to master lcore, but I can't find any code for setting the affinity of the specified thread. Here is my configuration: lscpu Architecture: x86_64 CPU op-mode(s):