[dpdk-users] [DPDK 20.11] rte_eal_init() appear additional thread

["Dong, Shaojie (NSB - CN/Hangzhou)" <shaojie.dong@nokia-sbell.com>]

Hi,  DPDK expert



We updated dpdk version from 18.05 to 20.11



Using following parameter to call  rte_eal_init() with secondary instance



dpdk_argc=5

dpdk_argv[0]=dpdk_monitor

dpdk_argv[1]=--proc-type=secondary

dpdk_argv[2]=--file-prefix=ccsrt_0x1231

dpdk_argv[3]=

dpdk_argv[4]=--no-pci


print from “ps -eL” for 20.11 version appear additional thread of dpdk_monitor
  518   518 pts/2    00:00:00 dpdk_monitor
  518   519 pts/2    00:00:00 eal-intr-thread
  518   520 pts/2    00:00:00 rte_mp_handle
  518   521 pts/2    00:00:00 lcore-worker-1
  518   522 pts/2    00:00:00 lcore-worker-2
  518   523 pts/2    00:00:00 lcore-worker-3
  518   524 pts/2    00:00:00 dpdk_monitor
  525   525 pts/4    00:00:00 ps


print from “ps -eL” for 18.05 version only one dpdk_monitor thread
  345   345 pts/1    00:00:00 dpdk_monitor
  345   346 pts/1    00:00:00 eal-intr-thread
  345   347 pts/1    00:00:00 rte_mp_handle
  345   348 pts/1    00:00:00 lcore-slave-1
  345   349 pts/1    00:00:00 lcore-slave-2
  345   350 pts/1    00:00:00 lcore-slave-3
  351   351 pts/3    00:00:00 ps


  //related code

   ret = rte_eal_init(dpdk_argc, (char**)dpdk_argv);



     if (ret < 0) {

         fprintf(stderr, "%s - Cannot init the DPDK EAL!, rte_eal_init returned %d\n",

                        __FUNCTION__, ret);

         proc_info_usage(argv[0]);

         return GLO_FALSE;

     }

     else {

         fprintf(stdout, "%s - ret_eal_init() successfull - lcore_id=%u\n",

                    __FUNCTION__, rte_lcore_id());

     }

//  rte_eal_init() log

EAL: Detected 24 lcore(s)

EAL: Detected 1 NUMA nodes

EAL: Multi-process socket /var/run/dpdk/ccsrt_0x1231/mp_socket_358_6dc4bc822f72

EAL: Selected IOVA mode 'PA'

EAL: Probing VFIO support...

EAL: WARNING: Address Space Layout Randomization (ASLR) is enabled in the kernel.

EAL:    This may cause issues with mapping memory into secondary processes

EAL: No legacy callbacks, legacy socket not created

main - ret_eal_init() successfull - lcore_id=0


Could you please how to avoid this additional thread ?


//Attach the primary instance log，primary instance also appear double Disp_0 threads on 20.11 version compare with 18.05 version’s one Disp_0 thread
ccs_em_init_rt_snf_env: Call rte_eal_init with options:
ccs_em_init_rt_snf_env:         -argv[0]= Disp_0
ccs_em_init_rt_snf_env:         -argv[1]= --lcores
ccs_em_init_rt_snf_env:         -argv[2]= 0@(0,1,2,3)
ccs_em_init_rt_snf_env:         -argv[3]= -v
ccs_em_init_rt_snf_env:         -argv[4]= -n
ccs_em_init_rt_snf_env:         -argv[5]= 2
ccs_em_init_rt_snf_env:         -argv[6]= -m
ccs_em_init_rt_snf_env:         -argv[7]= 3072
ccs_em_init_rt_snf_env:         -argv[8]= --huge-dir
ccs_em_init_rt_snf_env:         -argv[9]= /mnt/huge2M
ccs_em_init_rt_snf_env:         -argv[10]= --base-virtaddr
ccs_em_init_rt_snf_env:         -argv[11]= 0x6a0000000000
ccs_em_init_rt_snf_env:         -argv[12]= --legacy-mem
ccs_em_init_rt_snf_env:         -argv[13]=
ccs_em_init_rt_snf_env:         -argv[14]= --proc-type
ccs_em_init_rt_snf_env:         -argv[15]= primary
ccs_em_init_rt_snf_env:         -argv[16]= --file-prefix
ccs_em_init_rt_snf_env:         -argv[17]= ccsrt_0x1231
ccs_em_init_rt_snf_env:         -argv[18]=
ccs_em_init_rt_snf_env:         -argv[19]= -w
ccs_em_init_rt_snf_env:         -argv[20]= f4:00.1
ccs_em_init_rt_snf_env:         -argv[21]= -w
ccs_em_init_rt_snf_env:         -argv[22]= f4:00.2
ccs_em_init_rt_snf_env:         -argv[23]= -w
ccs_em_init_rt_snf_env:         -argv[24]= f4:00.3
ccs_em_init_rt_snf_env:         -argv[25]= -w
ccs_em_init_rt_snf_env:         -argv[26]= f4:00.4
ccs_em_init_rt_snf_env:         -argv[27]= -w
ccs_em_init_rt_snf_env:         -argv[28]= f4:00.5
ccs_em_init_rt_snf_env:         -argv[29]= -w
ccs_em_init_rt_snf_env:         -argv[30]= f4:00.6
ccs_em_rt_snf_init_sync: on core 3
EAL: No legacy callbacks, legacy socket not created
Debug/CCS/EM, dummy_thread:  - ret_eal_init() successfull - lcore_id=0

Many thanks !
Shaojie.Dong