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 A3006A00C5; Fri, 9 Dec 2022 22:14:37 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 92533410FB; Fri, 9 Dec 2022 22:14:37 +0100 (CET) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by mails.dpdk.org (Postfix) with ESMTP id 6F28940A8B for ; Fri, 9 Dec 2022 22:14:36 +0100 (CET) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 15ED55C0167; Fri, 9 Dec 2022 16:14:36 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Fri, 09 Dec 2022 16:14:36 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm2; t=1670620476; x= 1670706876; bh=+LI0X0Lr7kOizf7WfJyaXtQK5Dqrc0UVPuDwY5cWHTg=; b=I KGFuco2gWP8sA8p/Q53zJmRxT9LgwbgUHCAKmO6beZ909mtE9+Ok90HssddDVj5L J8Et6awsANufyqtxV/yb7ftuDUYIeMfuSuFolR0gx41clP7rlhWisKWNbwxndsOq td1uHuUYDrnmK4XUS3EKlTlgCObwUOT/y+JvyplMfw3r0LlZ4M3u8ih8+hSq+lOz 9XnscogCFYjeT06BM0eeBDUyo6AgABIa/BtbJ6rGKUB7DozfeAl+Y2n+KwhuyxZU bCOrBav53ZXf7iaP3XUIeyAN/UzwX8Vx/Odv+dDHpDlpm9t2jbJN1Lwk4VgM/THs pAt9eZ8vvuQuTr+xzfKhg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1670620476; x= 1670706876; bh=+LI0X0Lr7kOizf7WfJyaXtQK5Dqrc0UVPuDwY5cWHTg=; b=Q 7cQDccFqkqhX7iDzFxysdQlm7bzTotkwsKSXMVlF2cIwV7ou+omNfUTNdLeX3sgn TYB63hYxvCjEN6zpfx2W6eG2j241r2MHa355oTzzUxPZS7cZORkeZ8nE+EooE2Ce CGuFc9p1tF/pX/nvjquBMekpw8+o/8hTZ9dHYb6DQg7xQFoXksbQFVcF2yE0FkeF RhGDTuTO49T7n5Ax5BwxVJCbqKNJtgbtTvKRX4lzcxvAefCaAvyk+p0fwKCCxepl TMAW5sJeT3D3yB8HBxG0S2urhOSIyr18go+kSDXJigsG234UOQWvb9uAzBvVSQDY 7CvIDS+MmkZiW+izzUyPQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvddvgddugeegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpedtjeeiieefhedtfffgvdelteeufeefheeujefgueetfedttdei kefgkeduhedtgfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 9 Dec 2022 16:14:34 -0500 (EST) From: Thomas Monjalon To: Stephen Hemminger , Tyler Retzlaff Cc: Morten =?ISO-8859-1?Q?Br=F8rup?= , dev@dpdk.org, david.marchand@redhat.com, Bruce Richardson Subject: Re: help with pthread_t deprecation / api changes Date: Fri, 09 Dec 2022 22:14:33 +0100 Message-ID: <17965272.sWSEgdgrri@thomas> In-Reply-To: <20221209084814.3b1479d5@hermes.local> References: <20221130225427.GA13682@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> <2146119.C4sosBPzcN@thomas> <20221209084814.3b1479d5@hermes.local> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 09/12/2022 17:48, Stephen Hemminger: > On Fri, 09 Dec 2022 08:53:57 +0100 > Thomas Monjalon 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. What is missing exactly to have thread name in the core dump?