DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, Timothy McDaniel <timothy.mcdaniel@intel.com>,
	Shepard Siegel <shepard.siegel@atomicrules.com>,
	Ed Czeck <ed.czeck@atomicrules.com>,
	John Miller <john.miller@atomicrules.com>,
	Rosen Xu <rosen.xu@intel.com>, Matan Azrad <matan@nvidia.com>,
	Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
	Ori Kam <orika@nvidia.com>, Suanming Mou <suanmingm@nvidia.com>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Tianfei Zhang <tianfei.zhang@intel.com>,
	Xiao Wang <xiao.w.wang@intel.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	Chenbo Xia <chenbo.xia@intel.com>,
	Anatoly Burakov <anatoly.burakov@intel.com>,
	Bruce Richardson <bruce.richardson@intel.com>,
	Harman Kalra <hkalra@marvell.com>,
	Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
	Narcisa Ana Maria Vasile <navasile@linux.microsoft.com>,
	Dmitry Malloy <dmitrym@microsoft.com>,
	Pallavi Kadam <pallavi.kadam@intel.com>,
	Naga Harish K S V <s.v.naga.harish.k@intel.com>,
	Jerin Jacob <jerinj@marvell.com>,
	Ciara Power <ciara.power@intel.com>
Subject: Re: [PATCH] set namespace prefix to threads
Date: Mon, 03 Jul 2023 13:49:55 +0200	[thread overview]
Message-ID: <12236357.O9o76ZdvQC@thomas> (raw)
In-Reply-To: <CAJFAV8xm=erQH7p3RoJrOG69PDeucb_0n-V4Psb9BEjwE=9B4g@mail.gmail.com>

03/07/2023 13:38, David Marchand:
> On Mon, Jul 3, 2023 at 1:24 PM Thomas Monjalon <thomas@monjalon.net> wrote:
> >
> > When looking at threads in a system, it can be confusing
> > to find some unknown threads without a clue it is started by DPDK.
> >
> > Let's start all thread names with "dpdk-"
> > and the driver name if it comes from a driver.
> >
> > One more constraint: the thread names are generally limited
> > to 16 characters, including NUL character.
> 
> Yes, and no way to discover this limit.
> 
> 
> >
> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> > ---
> > Please review carefully, I may have missed things.
> >
> > Note: we should use rte_ctrl_thread_create() as much as possible.
> >
> 
> As for this comment, we should advertise rte_thread_create_control()
> instead, as it is thread library agnostic.
> Which leads me to suggest looking at rte_thread_create_control() calls too.

You're right, I'll do a second pass.

> > diff --git a/lib/eal/freebsd/eal.c b/lib/eal/freebsd/eal.c
> > index 7008303e11..e201acd1c2 100644
> > --- a/lib/eal/freebsd/eal.c
> > +++ b/lib/eal/freebsd/eal.c
> > @@ -843,7 +843,7 @@ rte_eal_init(int argc, char **argv)
> >
> >                 /* Set thread_name for aid in debugging. */
> >                 snprintf(thread_name, sizeof(thread_name),
> > -                               "rte-worker-%d", i);
> > +                               "dpdk-worker-%d", i);
> >                 rte_thread_set_name(lcore_config[i].thread_id, thread_name);
> >
> >                 ret = rte_thread_set_affinity_by_id(lcore_config[i].thread_id,
> 
> We changed this not so long ago with 8ae946970ed3 ("eal: fix thread
> name for high order lcores") which offered up to 4 digits for lcores.
> With your proposal, we are back to only 3 digits, which is probably
> enough, but I preferred to raise it.

In general no need of hyphen before a number.
I will change to dpdk-worker%d.



  reply	other threads:[~2023-07-03 11:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-03 11:23 Thomas Monjalon
2023-07-03 11:38 ` David Marchand
2023-07-03 11:49   ` Thomas Monjalon [this message]
2023-07-17 14:09     ` Bruce Richardson
2023-07-17 16:07       ` Thomas Monjalon
2023-07-17 16:14         ` Bruce Richardson
2023-07-03 12:14 ` [PATCH v2] " Thomas Monjalon
2023-07-04  9:18   ` fengchengwen
2023-07-10 18:42   ` Tyler Retzlaff
2023-08-31 14:37     ` Thomas Monjalon

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=12236357.O9o76ZdvQC@thomas \
    --to=thomas@monjalon.net \
    --cc=anatoly.burakov@intel.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=bruce.richardson@intel.com \
    --cc=chenbo.xia@intel.com \
    --cc=ciara.power@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=dmitrym@microsoft.com \
    --cc=ed.czeck@atomicrules.com \
    --cc=hkalra@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=john.miller@atomicrules.com \
    --cc=matan@nvidia.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=navasile@linux.microsoft.com \
    --cc=orika@nvidia.com \
    --cc=pallavi.kadam@intel.com \
    --cc=rosen.xu@intel.com \
    --cc=s.v.naga.harish.k@intel.com \
    --cc=shepard.siegel@atomicrules.com \
    --cc=suanmingm@nvidia.com \
    --cc=tianfei.zhang@intel.com \
    --cc=timothy.mcdaniel@intel.com \
    --cc=viacheslavo@nvidia.com \
    --cc=xiao.w.wang@intel.com \
    /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).