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 C91394247D; Tue, 24 Jan 2023 17:03:42 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6AA4540150; Tue, 24 Jan 2023 17:03:42 +0100 (CET) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by mails.dpdk.org (Postfix) with ESMTP id F2D8D400EF for ; Tue, 24 Jan 2023 17:03:41 +0100 (CET) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 7AA8D5C0425; Tue, 24 Jan 2023 11:03:41 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Tue, 24 Jan 2023 11:03:41 -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=fm3; t=1674576221; x= 1674662621; bh=5Kf7QdvOtRwQeWalnQM8JKrAVgGc355Wte7ammj43yc=; b=X P37xRsTokbl7IInR83EWtCBfQvNKTxmFgujEaFqdY9jv/xWbUQ8C1t8SCjploDgF 7zG2YQZ3MYgSZ5o5VyeX5ebbjEv1lci2kTxBL/EsVPd+6mKX8KGHlMeK6nde6tgP 6qRqwWthWdGZ371VbqtYrbF8xqq897Ji80vQdp5klxrqnBeqbnhk9HEoq43xQ3zG m/Rl0FTwx5qooFV1qUYfDzDLJ4eMBoSquNp3R7+5gPuFYtNyQY+3Hm0k6X4iRsIw Ss+pePG9bfeql2oSKQNABbO73aFjMy3IftpZnkEucQ+amYt9vzzCyru5mUyTO/c8 +DynnZDL3YXsRZQan+m9g== 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=fm3; t=1674576221; x= 1674662621; bh=5Kf7QdvOtRwQeWalnQM8JKrAVgGc355Wte7ammj43yc=; b=C xd2tntcHO4RPSN91wtHPSmKWv+jJpay1OxcgSYJ/XhkJ+p/TAzS6xS12pKSp3gh+ 4upNHM4PelGCW7IcnpKyxUiqCXdPDo8T37+9+u6ICo0F8GTX7SjUpJzhq88xn9gx 0UeejOeEeUbmRP7W6lwH9YsQN1lvYL6ugCewsCyefsR0VzgSqmK9xCwq0yikFq96 CzFDKOy937DF4Gd1ZO8UThr4iy667j3P9IfRRDpi7CQoDUyrWAdIP6nI/sWYL4PT qcnqho06LGXe3ImIa6C7fG7oAbA6ENj0m638VImBHzZKosM+sKDxAmGZEYYh4gsR Jinj8gVEsL0/EMiAT3/QQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedruddvtddgkedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvfevufffkfgjfhgggfgtsehtqh ertddttddunecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghs sehmohhnjhgrlhhonhdrnhgvtheqnecuggftrfgrthhtvghrnhepfefhjeeluedvvedtud dtuedtvefhieejtefhffeujefhteduudevtdektdeikeffnecuvehluhhsthgvrhfuihii vgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonh drnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 24 Jan 2023 11:03:40 -0500 (EST) From: Thomas Monjalon To: Tyler Retzlaff Cc: dev@dpdk.org, david.marchand@redhat.com, jerinjacobk@gmail.com, mb@smartsharesystems.com Subject: Re: [PATCH v7 5/5] eal: deprecation notice for rte thread setname API Date: Tue, 24 Jan 2023 17:03:39 +0100 Message-ID: <3536478.rnzMqkiUVr@thomas> In-Reply-To: <1674502774-20253-6-git-send-email-roretzla@linux.microsoft.com> References: <1670439617-9054-1-git-send-email-roretzla@linux.microsoft.com> <1674502774-20253-1-git-send-email-roretzla@linux.microsoft.com> <1674502774-20253-6-git-send-email-roretzla@linux.microsoft.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" 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 23/01/2023 20:39, Tyler Retzlaff: > Notify deprecation of rte_thread_setname API, it will be removed as it > exposes platform-specific thread details. The functionality it provided > is now available via the new rte_lcore_set_name API. >=20 > Signed-off-by: Tyler Retzlaff >=20 > Acked-by: Morten Br=F8rup > Acked-by: David Marchand >=20 > --- > doc/guides/rel_notes/deprecation.rst | 4 ++++ > 1 file changed, 4 insertions(+) >=20 > diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/= deprecation.rst > index e18ac34..2990bb1 100644 > --- a/doc/guides/rel_notes/deprecation.rst > +++ b/doc/guides/rel_notes/deprecation.rst > @@ -126,3 +126,7 @@ Deprecation Notices > Its removal has been postponed to let potential users report interest > in maintaining it. > In the absence of such interest, this library will be removed in DPDK = 23.11. > + > +* eal: The function ``rte_thread_setname`` will be removed, continuing > + the effort to decouple EAL from platform-specific thread > + implementations. You need to specify when it will be marked as deprecated and when it will be removed. You can mark it as deprecated when the replacement is not experimental. minor note: insert it near other EAL deprecations.