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 08FADA0032; Fri, 9 Dec 2022 17:48:20 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E427F410FB; Fri, 9 Dec 2022 17:48:19 +0100 (CET) Received: from mail-pj1-f54.google.com (mail-pj1-f54.google.com [209.85.216.54]) by mails.dpdk.org (Postfix) with ESMTP id 1AAF740A8B for <dev@dpdk.org>; Fri, 9 Dec 2022 17:48:17 +0100 (CET) Received: by mail-pj1-f54.google.com with SMTP id q17-20020a17090aa01100b002194cba32e9so8721509pjp.1 for <dev@dpdk.org>; Fri, 09 Dec 2022 08:48:17 -0800 (PST) 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 :message-id:reply-to; bh=7+c1g0NvIHONUfJoKwOhX5qJfFVQePMwyZXXu20rNJg=; b=NuixMcnodV1T5ifoJ+EgZM222KRu3mB8kd7M4lnPM3E29LVQnnvMyoACf6KEy0c9xV S7UeE/lppun/Aoi8YNfAcZSVC42qWb0YKUO7UvL9D1bYLji+7zaq1pNTxhHgGsQ8k8sI 6vou7EFnYTz6nVbmPVnhsUWviN4XhOC7oB9+KpvdbKfkGkQ07+sQOszSzZtuPwSebeS/ UPWRQP2NLZgu9M0HWjf3WQMPCtzWSFybvPBTZalQQnuF1yLKE1EWeaMseZN/T5JrCxLU kvrXOFKPSnRXGZAeF+iN0RcEj38YAj5ba2FVtj2VZY+k9haYcJePT+Udu3KEsh1zh3Tg Go/Q== 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:message-id:reply-to; bh=7+c1g0NvIHONUfJoKwOhX5qJfFVQePMwyZXXu20rNJg=; b=Rixf8fskizTqmsVEjqK5Cftxp3NnMAofdbrh3TJc4a8dW4iuq3NAVCGIMjKTHQfN1h Xav30XkrYhcLwr3YhwBx0H26cyDjhP0ky5+WEn9aggyHkzzWj6gGvz50ddCvfThPAApo 42j7TlN08Qn8t2X0hrSXhhgifshQB9ftZl65kRPQUmWdK6bKyCWlPTCQ4unFPClN2qOq 4BtVng1v/9Iktfhcyo0DNS+Qxp/plEciM+pmr9ZJqWlUnp/skF7uyzd8NxeicDYHHBWO zPUZ8gRyQabRo/WkaVQf9MN6BGZu2E+J5AnNxZv9/QZDi38Qc0oa7pmBCaPZ2DcuQEW+ KU1g== X-Gm-Message-State: ANoB5plkI3Yps9Smi63hsD+EefNKDa1MMHyKg5a7T+tsw6dwAHIn0eYl 8sjMrdJ9/kH9j9hvYJMRynZplw== X-Google-Smtp-Source: AA0mqf61eFHtz35E4zjFKm0UCkk0gHJ79PRvT7VA5fs2CsE9GdVXylXToolszHZKzhmuGo2uWZz3Qw== X-Received: by 2002:a17:90a:7789:b0:212:de1a:3559 with SMTP id v9-20020a17090a778900b00212de1a3559mr7819940pjk.8.1670604497177; Fri, 09 Dec 2022 08:48:17 -0800 (PST) Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218]) by smtp.gmail.com with ESMTPSA id f34-20020a17090a702500b0021806f631ccsm1339031pjk.30.2022.12.09.08.48.16 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 09 Dec 2022 08:48:16 -0800 (PST) Date: Fri, 9 Dec 2022 08:48:14 -0800 From: Stephen Hemminger <stephen@networkplumber.org> To: Thomas Monjalon <thomas@monjalon.net> Cc: Morten =?UTF-8?B?QnLDuHJ1cA==?= <mb@smartsharesystems.com>, Tyler Retzlaff <roretzla@linux.microsoft.com>, dev@dpdk.org, david.marchand@redhat.com, Bruce Richardson <bruce.richardson@intel.com> Subject: Re: help with pthread_t deprecation / api changes Message-ID: <20221209084814.3b1479d5@hermes.local> In-Reply-To: <2146119.C4sosBPzcN@thomas> References: <20221130225427.GA13682@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> <98CBD80474FA8B44BF855DF32C47DC35D8753E@smartserver.smartshare.dk> <20221202195750.GA28809@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> <2146119.C4sosBPzcN@thomas> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 Fri, 09 Dec 2022 08:53:57 +0100 Thomas Monjalon <thomas@monjalon.net> wrote: > > > If some execution environment doesn't support thread names, it could return a string that makes it possible for a human to identify the thread, e.g. the tread id. Again, this is assuming that it is only used for debugging, trace, and similar. > > > > i think this raises a good question. is the purpose of setting a thread name > > meant to be something we can use from the application or is it something that > > is for debugging diagnostics and may be a best effort? > > I think yes it is only for debugging. > So best effort looks to be a good approach. > I'm not sure you need to replace the functions. > Can you just complete the implementations? Surprisingly, thread names are not preserved in core dumps. The core dump standard used by Linux does not put thread name in the image. Since this is a ELF ABI unlikely to be ever be added.