Hello, David Thank you very much for your information !
I found DPDK version 21.05 set this thread name as "telemetry-v2" https://code.dpdk.org/dpdk/v21.05/source/lib/telemetry/telemetry.c#L541 -----Original Message----- From: David Marchand <[email protected]> Sent: Tuesday, August 17, 2021 5:26 PM To: Dong, Shaojie (NSB - CN/Hangzhou) <[email protected]> Cc: Stephen Hemminger <[email protected]>; [email protected]; Meunier, Julien (Nokia - FR/Paris-Saclay) <[email protected]> Subject: Re: [dpdk-users] [DPDK 20.11] rte_eal_init() appear additional thread On Tue, Aug 17, 2021 at 11:19 AM Dong, Shaojie (NSB - CN/Hangzhou) <[email protected]> wrote: > 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_cre > ate() > > 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 telemetry threads are renamed since 5da7736f8c53 ("telemetry: set socket listener thread name") (with a followup fix). -- David Marchand
