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 CEA21A00C5; Fri, 9 Dec 2022 22:13:52 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 66411410FB; Fri, 9 Dec 2022 22:13:52 +0100 (CET) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by mails.dpdk.org (Postfix) with ESMTP id B064640A8B for ; Fri, 9 Dec 2022 22:13:50 +0100 (CET) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 26E9E5C005D; Fri, 9 Dec 2022 16:13:48 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Fri, 09 Dec 2022 16:13:48 -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=1670620428; x= 1670706828; bh=6C6PJlydFsm7LUsGgy28j4PZBIrm2z//NdN7tnQGED8=; b=n SndXZLajupEflYaJrgyEpHPtWB0FzV2PY1E6MyvBro03R/n8OsxXA0+1Xy7zEYw+ NoAzwbq3FW2itrSRM1TlpkDzJhg1Qktt9rM6lPP0xvwv1lfwHJCO1E2894HOc1L1 Q6iG5KAH2b5pZerDpfqCFMTCc1kBz8r3aFE8phd71MQU8qBZ1COpmnXbyb42Iwd6 jStKsPuwnZ0waziK6+39o6uaY5BLfwdw/f3BSk7LVOs07EFeibuy7TSjp7sRhGkR V8XDOZsasaH1JrumGOHvVKlxMY4M9f9HBbWJa/pvEW0Y6XbdZi90s8eemCyOZePM Q1cOByKqPhFQs29ATJNsw== 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=1670620428; x= 1670706828; bh=6C6PJlydFsm7LUsGgy28j4PZBIrm2z//NdN7tnQGED8=; b=W E8oUYHRXHTLRBvAotvqLcA1GI9FmqTzWLezoUl3MgRn0CWhcJpM17ekPYpjcrOAN ulGhtyhLNe9SEHANM0CFTaJ44e4IVfYRtMPlpVjljCLwhp7F31DFIEQrfj4ZGy5W i3LKtbQZ3vW5ZeA3gy8/fPYYgP5lYc2GiQAwPWxGE4pM9y+Op2nxJwMVOC3KtqfJ px5lW7L/euKx3b9FsLO9BL9h601DJ9gEBpmSfLa0jj6Sthdl7AeZEZ+RnikYQysc KnJSvXlzgP2RNHDdU1Df5BOekHCwvQPqJAVfhoJIk+axm3uUngePD8z3GxdhIWur 9lb8fiEeKt6t+Nj9PLTPw== 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:13:46 -0500 (EST) From: Thomas Monjalon To: Tyler Retzlaff Cc: Stephen Hemminger , dev@dpdk.org, Morten =?ISO-8859-1?Q?Br=F8rup?= , david.marchand@redhat.com, Bruce Richardson Subject: Re: help with pthread_t deprecation / api changes Date: Fri, 09 Dec 2022 22:13:44 +0100 Message-ID: <6848416.18pcnM708K@thomas> In-Reply-To: <20221209200613.GB19263@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> References: <20221130225427.GA13682@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> <20221209084814.3b1479d5@hermes.local> <20221209200613.GB19263@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> 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 21:06, Tyler Retzlaff: > On Fri, Dec 09, 2022 at 08:48:14AM -0800, Stephen Hemminger wrote: > > 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? > > > > > > Thomas Monjalon wrote: > > > 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? > > the patch series put forward allows a set / get name per-lcore, where > you get implicit (but not exposed via the eal api) call to underlying > platform thread setname. I don't understand how lcore ID and thread ID are connected. You can run multiple control threads on a single lcore.