From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 66073A0548 for ; Tue, 17 Aug 2021 11:26:40 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 26C5B40DF5; Tue, 17 Aug 2021 11:26:40 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by mails.dpdk.org (Postfix) with ESMTP id 7AF784014E for ; Tue, 17 Aug 2021 11:26:39 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1629192399; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=VGrEVZvPT2LZnq4l66Dm7mqUlQMYDhoXcCMeRK5HfcE=; b=FqKoMPM8dwZFZ8zgCb4SuXz0w0f2pvUgbifyclCT6oAvbWrHVicTVH0rOUDUa/BrfqhjuT je97tKyMvnGNQRt8s0U4byo3gf/RqEuwLjV/hge3IWXK9MvCB9/+gL/4DthaJr+8rkZRfx jB9/N/KMKJqXR9bqXqOGnN4B5m+tSVU= Received: from mail-ua1-f71.google.com (mail-ua1-f71.google.com [209.85.222.71]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-197-SqLFc1o1MRS8RfuD9-CBVw-1; Tue, 17 Aug 2021 05:26:35 -0400 X-MC-Unique: SqLFc1o1MRS8RfuD9-CBVw-1 Received: by mail-ua1-f71.google.com with SMTP id b24-20020ab02398000000b002abb9087041so2660173uan.11 for ; Tue, 17 Aug 2021 02:26:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VGrEVZvPT2LZnq4l66Dm7mqUlQMYDhoXcCMeRK5HfcE=; b=fXwwsm6r5mOAZueKTBHaE2HXo6u0TqiQnYbGhkrHtMWtZMQqaGMi9G0rHkJ27mma+v rxKzolF545rRpLFz2ptuARVI99erLiT5S39cJabxkFOjQ+n/toToE1QFochvzjf7470e 55bR/iivBJ2Ux/qYQYDi6TlB+i6hHK6HC/XeR5NgDJe1KF5atYvPbVQKmGFT4E3ijdXZ 0ONTYcN2os6v1zPhgdWKqbI+nhQ+y+nGeiDUcBQTfmfc1zhW3lGfrnehQeQjbWyYfow9 nNhqBK+HpuoYENVSoD/XUEjswDR2XVQw6xEpd846zdM/QMwR4E1Jos/uE3dl3bRLnMip aXpg== X-Gm-Message-State: AOAM533ctkUnsJgM6tTyuTkPkP+lx1LdnTDgvwEWhvZ1aZ/GEwnSoRjQ W7koFeCn1CF00KtxM4sMRWgGy3HCMIsQJJhd6nJPr6C/40jDe6hpeIxwFbK7f0YtYTXerI47CxL ELx76SjWquAGLlpwVK5Tt3A== X-Received: by 2002:a67:ec98:: with SMTP id h24mr1829294vsp.10.1629192395380; Tue, 17 Aug 2021 02:26:35 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwdlsuYC+0XWga0mjPtYSXUK3P9LKMzrVkrCZByWHASf7KqgGRsnzQtW3MfXsMZb0D+k7eToyPm5r6n3a7piyI= X-Received: by 2002:a67:ec98:: with SMTP id h24mr1829278vsp.10.1629192395183; Tue, 17 Aug 2021 02:26:35 -0700 (PDT) MIME-Version: 1.0 References: <07b3151ab8ee4191b11ef563ddd31d1d@nokia-sbell.com> <20210816204352.5766b854@hermes.local> <2f3ddcfab1844606951e514b84c9d512@nokia-sbell.com> In-Reply-To: <2f3ddcfab1844606951e514b84c9d512@nokia-sbell.com> From: David Marchand Date: Tue, 17 Aug 2021 11:26:24 +0200 Message-ID: To: "Dong, Shaojie (NSB - CN/Hangzhou)" Cc: Stephen Hemminger , "users@dpdk.org" , "Meunier, Julien (Nokia - FR/Paris-Saclay)" Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dmarchan@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" On Tue, Aug 17, 2021 at 11:19 AM Dong, Shaojie (NSB - CN/Hangzhou) wrote: > 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 telemetry threads are renamed since 5da7736f8c53 ("telemetry: set socket listener thread name") (with a followup fix). -- David Marchand