From: Stephen Hemminger <stephen@networkplumber.org>
To: "Dong, Shaojie (NSB - CN/Hangzhou)" <shaojie.dong@nokia-sbell.com>
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 08:24:18 -0700 [thread overview]
Message-ID: <20210817082418.464ac8c6@hermes.local> (raw)
In-Reply-To: <2f3ddcfab1844606951e514b84c9d512@nokia-sbell.com>
On Tue, 17 Aug 2021 09:19:40 +0000
"Dong, Shaojie (NSB - CN/Hangzhou)" <shaojie.dong@nokia-sbell.com> wrote:
> 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
The telemetry should be optional.
The thread name doesn't matter, it is only there for ps.
If you know the thread id, you can change it with pthread_setname_np
prev parent reply other threads:[~2021-08-17 15:24 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)
2021-08-17 9:26 ` David Marchand
2021-08-18 1:53 ` Dong, Shaojie (NSB - CN/Hangzhou)
2021-08-17 15:24 ` Stephen Hemminger [this message]
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=20210817082418.464ac8c6@hermes.local \
--to=stephen@networkplumber.org \
--cc=julien.meunier@nokia.com \
--cc=shaojie.dong@nokia-sbell.com \
--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).