From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <users-bounces@dpdk.org> Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 95AE7A0548 for <public@inbox.dpdk.org>; Tue, 17 Aug 2021 17:24:23 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 4C4DB40DF5; Tue, 17 Aug 2021 17:24:23 +0200 (CEST) Received: from mail-pj1-f52.google.com (mail-pj1-f52.google.com [209.85.216.52]) by mails.dpdk.org (Postfix) with ESMTP id 519014014E for <users@dpdk.org>; Tue, 17 Aug 2021 17:24:22 +0200 (CEST) Received: by mail-pj1-f52.google.com with SMTP id j12-20020a17090aeb0c00b00179530520b3so5869735pjz.0 for <users@dpdk.org>; Tue, 17 Aug 2021 08:24:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=Jstpnyr6BxXQTI65hRhcS3+KjScQMEgNbqhU4Sh6pYY=; b=D/dPsZoLM2G4c+3+oGdV0iC46Va06H8XG9MzVW9t5t4E5JIUAnquYrVnhhZGegEXRa atocHl6NAHAPetjlGbEFhOmYhMJogZl/fpxl0Dk0Meghw5BKrZdmSZJydSf5dlS4Q6sX LE2yur2ldfJcEw74o/YvEJuJ+93AW5irT8fDZDLGuUw+nF8j/wBhpuf9RHOibCU7TMdu X4ABkQsc7LAUhIgYKA0p4OHJ/MwvEseQpSJPcSzWujQykpueGe1s9w0rN2qnyyDb/Zko nPpVq9YUrt6JJ3THrClkz75epNDM9yBCIFQQff57p2x9Jaz7tiAFEZJVSGRHU20HS8r5 aGCA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=Jstpnyr6BxXQTI65hRhcS3+KjScQMEgNbqhU4Sh6pYY=; b=a/LTVZwAQwgadNVWarVH9Lyo8W33+6GkCm7vSdnKvdwauWaYnuI4Z18CneoEZPCnix hlP5g4mZA1gnuP+ysAiEA3cc29gIkqSLd9DLjWqCxsKAMBguDTxCcIXe0SmA6T1vFyUF FctU09M4wSJZQ20EE9FViKVQCvY7WR0ARoSV03lJL4Fh8mPOCCwy/A3FHhQ3iA/qsgg1 j8Zwmlz9/GBat3JBJW1iV12PLekiw1z0OgVQfJTj6kY/5MIZeF6SgNJN/8CyLLvlZzib q1UnEwF9jwPzXhntFZ7rJCcvw7KYRM2UkWP+c7YUMp9r+E5NMfwoh1Kplf2sA1uI5A+P RIlw== X-Gm-Message-State: AOAM533O9lzXnbO2nCNsPRall8b8zaSAGYHU1Csyv5iXwpxBhDYyE+9I xFPje313mur2R+UqzTJhNL4Asw== X-Google-Smtp-Source: ABdhPJzqQVMfSZoAxLIzvjQdKgNjV+251OwVXcdSOxNIUHhSZUVHD/NnGW1fSqE2+hnFoDzHSTj9jQ== X-Received: by 2002:a17:90a:f416:: with SMTP id ch22mr3897238pjb.128.1629213861188; Tue, 17 Aug 2021 08:24:21 -0700 (PDT) Received: from hermes.local (204-195-33-123.wavecable.com. [204.195.33.123]) by smtp.gmail.com with ESMTPSA id b17sm3180320pgl.61.2021.08.17.08.24.20 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 17 Aug 2021 08:24:20 -0700 (PDT) Date: Tue, 17 Aug 2021 08:24:18 -0700 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> Message-ID: <20210817082418.464ac8c6@hermes.local> In-Reply-To: <2f3ddcfab1844606951e514b84c9d512@nokia-sbell.com> References: <07b3151ab8ee4191b11ef563ddd31d1d@nokia-sbell.com> <20210816204352.5766b854@hermes.local> <2f3ddcfab1844606951e514b84c9d512@nokia-sbell.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-users] [DPDK 20.11] rte_eal_init() appear additional thread X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions <users.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/users>, <mailto:users-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/users/> List-Post: <mailto:users@dpdk.org> List-Help: <mailto:users-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/users>, <mailto:users-request@dpdk.org?subject=subscribe> Errors-To: users-bounces@dpdk.org Sender: "users" <users-bounces@dpdk.org> 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