From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
by inbox.dpdk.org (Postfix) with ESMTP id A997CA0543;
Thu, 22 Sep 2022 17:18:48 +0200 (CEST)
Received: from [217.70.189.124] (localhost [127.0.0.1])
by mails.dpdk.org (Postfix) with ESMTP id 41ECC40156;
Thu, 22 Sep 2022 17:18:48 +0200 (CEST)
Received: from mail-pl1-f180.google.com (mail-pl1-f180.google.com
[209.85.214.180])
by mails.dpdk.org (Postfix) with ESMTP id 5CF00400D7
for <dev@dpdk.org>; Thu, 22 Sep 2022 17:18:46 +0200 (CEST)
Received: by mail-pl1-f180.google.com with SMTP id w10so8201544pll.11
for <dev@dpdk.org>; Thu, 22 Sep 2022 08:18:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=networkplumber-org.20210112.gappssmtp.com; s=20210112;
h=content-transfer-encoding:mime-version:references:in-reply-to
:message-id:subject:cc:to:from:date:from:to:cc:subject:date;
bh=iMx/9FRhNayP/6r70g+hQg2jWcQvPW5I7wb9WiaHD88=;
b=5OV1ElC/LueMqypro7R8M7k8Ns8dmfEQ2fRF1kRrJqQJGDcn0187gd4l92Do6g/Zv5
IZhV8tOkDzjhIhBWlitgoBbc90sSUu7cIcY/SAftzvYlGLv3Feej5SHYpCEkehAEuMrY
SvCXCtCQ52CgkSaF5XlIgbDCmLLh+qH7+TfbWRXTgZ9AMmUkSd9WIsssNBfQ2x0yPtG6
kML1f5b8xtolZs1ZwStfKM7MHWE9OGtiB3KKzaeyBSLcn7AwF98OgdiP2fhOsCdNAtGi
9omy8L35N81klHNqymCPIseXW3xAh4xv74M/nHD+kJDrA2SbLwnemTXBOPRVoZGGAW5j
5VJw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20210112;
h=content-transfer-encoding:mime-version:references:in-reply-to
:message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc
:subject:date;
bh=iMx/9FRhNayP/6r70g+hQg2jWcQvPW5I7wb9WiaHD88=;
b=zcaVlvfoIe+t5FkxfQdUFKGlOl+qwZRWFIkyc4mNemBV2ApvGl5QavTkNOCOrJT94Q
aWRn+hHNIf74ljaQGTlVGCTS/ORXRBOEWvsAPDO9dn4+rYQ47Rs3nTG1tqwqYEBCZKId
pZctboeYIX9YXjFldeSQTS96G4VUw0yJJz8yXB3IdpMnQzj2yHVZw+/mjW0nZYcQ8iun
GtSCDIeBrSTSNqpdyJLdtqStvT4Tupnszfyhp2Op+zn/SOc8EiXbaVs9jlx+yk96TST7
YBaBa00WqWPikDxCbw6TrjKdF6j8bWE0+orxlzDzRQ9LB+tXX7l6XUO3e1BVjnXpiorV
8rgA==
X-Gm-Message-State: ACrzQf0D62C2+MOhaPiIOwuM/zD2FG2A+/QB7wznvoDu61mcFpW7/gJT
MPbh1itvKwyPrJ7vEpR5vYMaFA==
X-Google-Smtp-Source: AMsMyM719fTfZ1fdAMXFTE9+MQwAhUS8DUSnTVOP+kASjtRsXooTyry6k0BrVg2HlMX3vRFf/npZDw==
X-Received: by 2002:a17:902:f684:b0:178:84d:ddc5 with SMTP id
l4-20020a170902f68400b00178084dddc5mr3832298plg.62.1663859925384;
Thu, 22 Sep 2022 08:18:45 -0700 (PDT)
Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218])
by smtp.gmail.com with ESMTPSA id
x23-20020aa78f17000000b00540a3252191sm4558570pfr.28.2022.09.22.08.18.44
(version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
Thu, 22 Sep 2022 08:18:44 -0700 (PDT)
Date: Thu, 22 Sep 2022 08:18:43 -0700
From: Stephen Hemminger <stephen@networkplumber.org>
To: Abdullah =?UTF-8?B?w5ZtZXIgWWFtYcOn?= <omer.yamac@ceng.metu.edu.tr>
Cc: dev@dpdk.org, ferruh.yigit@xilinx.com, David Marchand
<david.marchand@redhat.com>
Subject: Re: [PATCH v2] lib/eal/linux: update lcore-worker name due to high
number of cores
Message-ID: <20220922081843.50b6d22e@hermes.local>
In-Reply-To: <20220922103023.499233-1-omer.yamac@ceng.metu.edu.tr>
References: <20220922101824.498149-1-omer.yamac@ceng.metu.edu.tr>
<20220922103023.499233-1-omer.yamac@ceng.metu.edu.tr>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
<mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
<mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
On Thu, 22 Sep 2022 13:30:23 +0300
Abdullah =C3=96mer Yama=C3=A7 <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.
>=20
> Signed-off-by: Abdullah =C3=96mer Yama=C3=A7 <omer.yamac@ceng.metu.edu.tr>
>=20
> ---
> Cc: David Marchand <david.marchand@redhat.com>
> ---
> lib/eal/linux/eal.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>=20
> 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)
> =20
> /* Set thread_name for aid in debugging. */
> snprintf(thread_name, sizeof(thread_name),
> - "lcore-worker-%d", i);
> + "rte-worker-%d", i);
> ret =3D rte_thread_setname(lcore_config[i].thread_id,
> thread_name);
> if (ret !=3D 0)
BSD should be setting name as well.
Acked-by: Stephen Hemminger <stephen@networkplumber.org>