From: Kevin Traynor <ktraynor@redhat.com>
To: "David Marchand" <david.marchand@redhat.com>,
"Abdullah Ömer Yamaç" <omer.yamac@ceng.metu.edu.tr>,
"Luca Boccassi" <bluca@debian.org>,
"Xueming(Steven) Li" <xuemingl@nvidia.com>,
"Christian Ehrhardt" <christian.ehrhardt@canonical.com>
Cc: dev@dpdk.org, ferruh.yigit@xilinx.com,
Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH v3] eal: update lcore-worker name due to high number of cores
Date: Mon, 26 Sep 2022 11:44:56 +0100 [thread overview]
Message-ID: <0d5dd85b-8fb5-3526-df9c-6e1ca23b1646@redhat.com> (raw)
In-Reply-To: <CAJFAV8xXJ55KB1u3CsJR8z2sB+Z4UA_h-Dh-DENkwmKmx-mPDA@mail.gmail.com>
On 26/09/2022 10:39, David Marchand wrote:
> Hello,
>
> On Fri, Sep 23, 2022 at 9:06 AM Abdullah Ömer Yamaç
> <omer.yamac@ceng.metu.edu.tr> wrote:
>>
>> In this patch we suggest a new name for lcore-worker.
>> In case of more than 99 logical cores, name is truncated
>> (length is restricted to 16 characters, including the
>> terminating null byte ('\0')) and it makes hard to follow threads.
>>
>> Signed-off-by: Abdullah Ömer Yamaç <omer.yamac@ceng.metu.edu.tr>
>> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
>
> - Thanks, good catch.
>
> Some comments though.
> What matters is the lcore index, not the core/lcore count.
> The commitlog could probably describe this better.
>
> For example, this issue can be triggered with --lcores=0,10@1,100@2
> and here we only have three lcores.
> $ cat /proc/$(pidof dpdk-testpmd)/task/*/comm
> dpdk-testpmd
> eal-intr-thread
> rte_mp_handle
> lcore-worker-10
> lcore-worker-10
> telemetry-v2
> telemetry-v1
>
>
> And what do you think of following title:
> "eal: fix thread names for high order lcores"
>
> Can you update the release notes?
>
>
> - Question to stable maintainers:
> Do you think we should backport this fix?
> As you can see below, this change affects EAL thread names, maybe some
> users are monitoring them based on the names...
>
No strong opinion, but backporting will change the name for any user who
looks at this and only fix an issue for users using lcore names 100+. So
would be inclined not to backport unless someone complains it is causing
a real issue for their use case.
>
>>
>> ---
>> Cc: David Marchand <david.marchand@redhat.com>
>> ---
>> lib/eal/freebsd/eal.c | 2 +-
>> lib/eal/linux/eal.c | 2 +-
>> 2 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/lib/eal/freebsd/eal.c b/lib/eal/freebsd/eal.c
>> index ee5c929da8..a1bb5363b1 100644
>> --- a/lib/eal/freebsd/eal.c
>> +++ b/lib/eal/freebsd/eal.c
>> @@ -817,7 +817,7 @@ rte_eal_init(int argc, char **argv)
>>
>> /* Set thread_name for aid in debugging. */
>> snprintf(thread_name, sizeof(thread_name),
>> - "lcore-worker-%d", i);
>> + "rte-worker-%d", i);
>> rte_thread_setname(lcore_config[i].thread_id, thread_name);
>>
>> ret = pthread_setaffinity_np(lcore_config[i].thread_id,
>> diff --git a/lib/eal/linux/eal.c b/lib/eal/linux/eal.c
>> index 46bf52cef0..9a168b7773 100644
>> --- a/lib/eal/linux/eal.c
>> +++ b/lib/eal/linux/eal.c
>> @@ -1248,7 +1248,7 @@ rte_eal_init(int argc, char **argv)
>>
>> /* Set thread_name for aid in debugging. */
>> snprintf(thread_name, sizeof(thread_name),
>> - "lcore-worker-%d", i);
>> + "rte-worker-%d", i);
>> ret = rte_thread_setname(lcore_config[i].thread_id,
>> thread_name);
>> if (ret != 0)
>> --
>> 2.27.0
>>
>
> Merci !
>
prev parent reply other threads:[~2022-09-26 10:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 10:18 [PATCH] Update " Abdullah Ömer Yamaç
2022-09-22 10:30 ` [PATCH v2] lib/eal/linux: update " Abdullah Ömer Yamaç
2022-09-22 15:18 ` Stephen Hemminger
2022-09-23 7:06 ` [PATCH v3] eal: " Abdullah Ömer Yamaç
2022-09-26 9:39 ` David Marchand
2022-09-26 9:56 ` [PATCH v4] eal: fix thread names for high order lcores Abdullah Ömer Yamaç
2022-09-26 10:03 ` [PATCH v5] " Abdullah Ömer Yamaç
2022-09-30 8:52 ` David Marchand
2022-09-26 10:44 ` Kevin Traynor [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=0d5dd85b-8fb5-3526-df9c-6e1ca23b1646@redhat.com \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@xilinx.com \
--cc=omer.yamac@ceng.metu.edu.tr \
--cc=stephen@networkplumber.org \
--cc=xuemingl@nvidia.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).