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

[Dong, Shaojie (NSB - CN/Hangzhou)]

Hi, Stephen

Thanks for your quickliy reply

I found the additional thread was created by following path on DPDK 20.11 version

rte_eal_init()->rte_telemetry_init()->telemetry_v2_init()->pthread_create()

Only call pthread_create() function to create this additional thread and then sleep all the time
DPDK code do not set this thread's name
So it inherits the main thread's name

Two threads with the same name are easy to confuse by business code
Does DPDK code support its name change ?

It was not worker/slave thread

-----Original Message-----
From: Stephen Hemminger <stephen at networkplumber.org> 
Sent: Tuesday, August 17, 2021 11:44 AM
To: Dong, Shaojie (NSB - CN/Hangzhou) <shaojie.dong at nokia-sbell.com>
Cc: users at dpdk.org; Meunier, Julien (Nokia - FR/Paris-Saclay) <julien.meunier at nokia.com>
Subject: Re: [dpdk-users] [DPDK 20.11] rte_eal_init() appear additional thread

On Tue, 17 Aug 2021 01:51:14 +0000
"Dong, Shaojie (NSB - CN/Hangzhou)" <shaojie.dong at nokia-sbell.com> wrote:

> Hi,  DPDK expert
> 
> 
> 
> We updated dpdk version from 18.05 to 20.11
> 
> 
> 
> Using following parameter to call  rte_eal_init() with secondary 
> instance

Which additional thread? When you start rte_eal_init it needs to create several additional sleeping thread for monitoring.

If you don't want the worker/slave threads then either only use a cpuset with a single CPU, or don't call rte_eal_launch()