From: David Marchand <david.marchand@redhat.com>
To: "Abdullah Ömer Yamaç" <omer.yamac@ceng.metu.edu.tr>
Cc: dev@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH v5] eal: fix thread names for high order lcores
Date: Fri, 30 Sep 2022 10:52:58 +0200 [thread overview]
Message-ID: <CAJFAV8y1V49tYTOYL=Ujxmy5brZZMsAhZEbzSJPdrimaFijHcQ@mail.gmail.com> (raw)
In-Reply-To: <20220926100314.1115507-1-omer.yamac@ceng.metu.edu.tr>
On Mon, Sep 26, 2022 at 12:03 PM Abdullah Ömer Yamaç
<omer.yamac@ceng.metu.edu.tr> wrote:
>
> In this patch we suggest a new name for lcore-worker.
> In case of higher order (greater 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.
>
> Ex: This issue can be generated using following arguments:
> --lcores=0,10@1,100@2
> Then we have;
> lcore-worker-10
> lcore-worker-10
>
> Signed-off-by: Abdullah Ömer Yamaç <omer.yamac@ceng.metu.edu.tr>
> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
Applied, with a note in the RN.
Thanks.
--
David Marchand
next prev parent reply other threads:[~2022-09-30 8:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 10:18 [PATCH] Update lcore-worker name due to high number of cores 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 [this message]
2022-09-26 10:44 ` [PATCH v3] eal: update lcore-worker name due to high number of cores Kevin Traynor
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='CAJFAV8y1V49tYTOYL=Ujxmy5brZZMsAhZEbzSJPdrimaFijHcQ@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=omer.yamac@ceng.metu.edu.tr \
--cc=stephen@networkplumber.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).