DPDK usage discussions
 help / color / mirror / Atom feed
From: "Dong, Shaojie (NSB - CN/Hangzhou)" <shaojie.dong@nokia-sbell.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "users@dpdk.org" <users@dpdk.org>,
	"Meunier,
	Julien (Nokia - FR/Paris-Saclay)" <julien.meunier@nokia.com>
Subject: Re: [dpdk-users] [DPDK 20.11] rte_eal_init() appear additional thread
Date: Tue, 17 Aug 2021 09:19:40 +0000	[thread overview]
Message-ID: <2f3ddcfab1844606951e514b84c9d512@nokia-sbell.com> (raw)
In-Reply-To: <20210816204352.5766b854@hermes.local>

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@networkplumber.org> 
Sent: Tuesday, August 17, 2021 11:44 AM
To: Dong, Shaojie (NSB - CN/Hangzhou) <shaojie.dong@nokia-sbell.com>
Cc: users@dpdk.org; Meunier, Julien (Nokia - FR/Paris-Saclay) <julien.meunier@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@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()

 

  reply	other threads:[~2021-08-17  9:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-17  1:51 Dong, Shaojie (NSB - CN/Hangzhou)
2021-08-17  3:43 ` Stephen Hemminger
2021-08-17  9:19   ` Dong, Shaojie (NSB - CN/Hangzhou) [this message]
2021-08-17  9:26     ` David Marchand
2021-08-18  1:53       ` Dong, Shaojie (NSB - CN/Hangzhou)
2021-08-17 15:24     ` Stephen Hemminger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2f3ddcfab1844606951e514b84c9d512@nokia-sbell.com \
    --to=shaojie.dong@nokia-sbell.com \
    --cc=julien.meunier@nokia.com \
    --cc=stephen@networkplumber.org \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).