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 B81CB431FC for ; Wed, 25 Oct 2023 18:34:14 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 165E742DD2; Wed, 25 Oct 2023 18:34:12 +0200 (CEST) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) by mails.dpdk.org (Postfix) with ESMTP id 2E0AA42DD3; Wed, 25 Oct 2023 18:34:10 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 64609320092B; Wed, 25 Oct 2023 12:34:08 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 25 Oct 2023 12:34:09 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type: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= 1698251647; x=1698338047; bh=xkL8LhS59FQYXzaYOnKxKAebwrH0YVddcdk ncaIjb90=; b=bhazlTRV29fqSq+utgrJcOe7lOP2snffjJCxJy60rQToe9SYOlp gna4QUHmplMdmJmU6QdkfHd8xEloYK2Ri/YXotu6hoy7RTtqO5udyaUYyqmcirTg i4o3u5MpmnnGBAKakW3i6l04gZ0DW31Y6nOlArJdomYgINnjZbxd3/w91bUbI3Ve OPb0zO4RQPrZ800eSHb2l4Xm5wKjbvpoVdDuqZ41lK/AFMGX3UVVDQZZ7vOvZw+8 CYRzeFbqYJEMUWzjsk3QssSTIdodgv8ydKVvkJ9+710+czIZb+MtXUIyoHDy6XVQ Ff9VexRe+MWkHYata6dVYR0uc4q0HHy0G5g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type: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= 1698251647; x=1698338047; bh=xkL8LhS59FQYXzaYOnKxKAebwrH0YVddcdk ncaIjb90=; b=vzAA2NEMdWoban+a+wg5r+lRO3JRrl7+e2RPf7ZtXTuIxKS4MOA Ay0PCHy08we2D3wVlKafKPk39TPmzV8y+QyuK5Utsv+nPfG2G6sd50TeYoQizY5z 1fSC8ckVTCzUeIcJrDJIVIaWsnO3BZDdvJtKg0KeswCpxke20sz4NRQVmHFq+aWR UkuAowiLrGyUJ+nWrJTouX43YwCaR9897U6WgN0TYyCrr9ga40iuwm+OFlFGOHWw CzTfbmPIEgtbFH+K9pFyGxwPcKM4r8ebSAXWtz9397I5F5IsV/2P8VwHihpe3mt4 D+5YrQxz6kOiS8uff4GRDUYXjCFEKroaeSw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrledtgddutdduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkofgjfhggtgfgsehtkeertdertdejnecuhfhrohhmpefvhhho mhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqne cuggftrfgrthhtvghrnheptdeiffffgeefteelhfekueetueduffejgfelvedtieejudek gfevheetheehgeejnecuvehluhhsthgvrhfuihiivgepudenucfrrghrrghmpehmrghilh hfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 25 Oct 2023 12:34:05 -0400 (EDT) From: Thomas Monjalon To: dev@dpdk.org Cc: David Marchand , stable@dpdk.org, =?UTF-8?q?Morten=20Br=C3=B8rup?= , Anatoly Burakov , Stephen Hemminger , Tyler Retzlaff , Narcisa Vasile , Dmitry Kozlyuk , Andrew Rybchenko , Konstantin Ananyev Subject: [PATCH v3 2/2] eal/unix: allow creating thread with real-time priority Date: Wed, 25 Oct 2023 18:31:11 +0200 Message-ID: <20231025163352.1076755-3-thomas@monjalon.net> X-Mailer: git-send-email 2.42.0 In-Reply-To: <20231025163352.1076755-1-thomas@monjalon.net> References: <20231024125416.798897-1-thomas@monjalon.net> <20231025163352.1076755-1-thomas@monjalon.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org When adding an API for creating threads, the real-time priority has been forbidden on Unix. There is a known issue with ring behaviour, but it should not be completely forbidden. Real-time thread can block some kernel threads on the same core, making the system unstable. That's why a pause is added in the test thread. Fixes: ca04c78b6262 ("eal: get/set thread priority per thread identifier") Fixes: ce6e911d20f6 ("eal: add thread lifetime API") Fixes: a7ba40b2b1bf ("drivers: convert to internal control threads") Cc: stable@dpdk.org Signed-off-by: Thomas Monjalon Acked-by: Morten Brørup --- app/test/test_threads.c | 11 +---------- doc/guides/prog_guide/env_abstraction_layer.rst | 4 +++- lib/eal/include/rte_thread.h | 7 +++++-- lib/eal/unix/rte_thread.c | 14 +++++--------- 4 files changed, 14 insertions(+), 22 deletions(-) diff --git a/app/test/test_threads.c b/app/test/test_threads.c index 4ac3f2671a..c14d39fc83 100644 --- a/app/test/test_threads.c +++ b/app/test/test_threads.c @@ -22,7 +22,7 @@ thread_main(void *arg) __atomic_store_n(&thread_id_ready, 1, __ATOMIC_RELEASE); while (__atomic_load_n(&thread_id_ready, __ATOMIC_ACQUIRE) == 1) - ; + rte_thread_yield_realtime(); /* required for RT priority */ return 0; } @@ -97,21 +97,12 @@ test_thread_priority(void) "Priority set mismatches priority get"); priority = RTE_THREAD_PRIORITY_REALTIME_CRITICAL; -#ifndef RTE_EXEC_ENV_WINDOWS - RTE_TEST_ASSERT(rte_thread_set_priority(thread_id, priority) == ENOTSUP, - "Priority set to critical should fail"); - RTE_TEST_ASSERT(rte_thread_get_priority(thread_id, &priority) == 0, - "Failed to get thread priority"); - RTE_TEST_ASSERT(priority == RTE_THREAD_PRIORITY_NORMAL, - "Failed set to critical should have retained normal"); -#else RTE_TEST_ASSERT(rte_thread_set_priority(thread_id, priority) == 0, "Priority set to critical should succeed"); RTE_TEST_ASSERT(rte_thread_get_priority(thread_id, &priority) == 0, "Failed to get thread priority"); RTE_TEST_ASSERT(priority == RTE_THREAD_PRIORITY_REALTIME_CRITICAL, "Priority set mismatches priority get"); -#endif priority = RTE_THREAD_PRIORITY_NORMAL; RTE_TEST_ASSERT(rte_thread_set_priority(thread_id, priority) == 0, diff --git a/doc/guides/prog_guide/env_abstraction_layer.rst b/doc/guides/prog_guide/env_abstraction_layer.rst index 6debf54efb..d1f7cae7cd 100644 --- a/doc/guides/prog_guide/env_abstraction_layer.rst +++ b/doc/guides/prog_guide/env_abstraction_layer.rst @@ -815,7 +815,9 @@ Known Issues 4. It MAY be used by preemptible multi-producer and/or preemptible multi-consumer pthreads whose scheduling policy are all SCHED_OTHER(cfs), SCHED_IDLE or SCHED_BATCH. User SHOULD be aware of the performance penalty before using it. - 5. It MUST not be used by multi-producer/consumer pthreads, whose scheduling policies are SCHED_FIFO or SCHED_RR. + 5. It MUST not be used by multi-producer/consumer pthreads + whose scheduling policies are ``SCHED_FIFO`` + or ``SCHED_RR`` (``RTE_THREAD_PRIORITY_REALTIME_CRITICAL``). Alternatively, applications can use the lock-free stack mempool handler. When considering this handler, note that: diff --git a/lib/eal/include/rte_thread.h b/lib/eal/include/rte_thread.h index 139cafac96..1952a10155 100644 --- a/lib/eal/include/rte_thread.h +++ b/lib/eal/include/rte_thread.h @@ -56,10 +56,13 @@ typedef uint32_t (*rte_thread_func) (void *arg); * Thread priority values. */ enum rte_thread_priority { + /** Normal thread priority, the default. */ RTE_THREAD_PRIORITY_NORMAL = 0, - /**< normal thread priority, the default */ + /** + * Highest thread priority, use with caution. + * WARNING: System may be unstable because of a real-time busy loop. + */ RTE_THREAD_PRIORITY_REALTIME_CRITICAL = 1, - /**< highest thread priority allowed */ }; /** diff --git a/lib/eal/unix/rte_thread.c b/lib/eal/unix/rte_thread.c index 92b4e53adb..87ddf25f1c 100644 --- a/lib/eal/unix/rte_thread.c +++ b/lib/eal/unix/rte_thread.c @@ -51,6 +51,11 @@ thread_map_priority_to_os_value(enum rte_thread_priority eal_pri, int *os_pri, sched_get_priority_max(SCHED_OTHER)) / 2; break; case RTE_THREAD_PRIORITY_REALTIME_CRITICAL: + /* + * WARNING: Real-time busy loop takes priority on kernel threads, + * making the system unstable. + * There is also a known issue when using rte_ring. + */ *pol = SCHED_RR; *os_pri = sched_get_priority_max(SCHED_RR); break; @@ -155,11 +160,6 @@ rte_thread_create(rte_thread_t *thread_id, goto cleanup; } - if (thread_attr->priority == - RTE_THREAD_PRIORITY_REALTIME_CRITICAL) { - ret = ENOTSUP; - goto cleanup; - } ret = thread_map_priority_to_os_value(thread_attr->priority, ¶m.sched_priority, &policy); if (ret != 0) @@ -291,10 +291,6 @@ rte_thread_set_priority(rte_thread_t thread_id, int policy; int ret; - /* Realtime priority can cause crashes on non-Windows platforms. */ - if (priority == RTE_THREAD_PRIORITY_REALTIME_CRITICAL) - return ENOTSUP; - ret = thread_map_priority_to_os_value(priority, ¶m.sched_priority, &policy); if (ret != 0) -- 2.42.0