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 80C9743208;
	Thu, 26 Oct 2023 15:44:53 +0200 (CEST)
Received: from mails.dpdk.org (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 6DB1B402EE;
	Thu, 26 Oct 2023 15:44:53 +0200 (CEST)
Received: from dkmailrelay1.smartsharesystems.com
 (smartserver.smartsharesystems.com [77.243.40.215])
 by mails.dpdk.org (Postfix) with ESMTP id D6543402CF
 for <dev@dpdk.org>; Thu, 26 Oct 2023 15:44:51 +0200 (CEST)
Received: from smartserver.smartsharesystems.com
 (smartserver.smartsharesys.local [192.168.4.10])
 by dkmailrelay1.smartsharesystems.com (Postfix) with ESMTP id E5FE9205C3;
 Thu, 26 Oct 2023 15:44:50 +0200 (CEST)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PATCH v3 0/2] allow creating thread with real-time priority
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Thu, 26 Oct 2023 15:44:50 +0200
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9EF99@smartserver.smartshare.dk>
In-Reply-To: <2170731.Icojqenx9y@thomas>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PATCH v3 0/2] allow creating thread with real-time priority
Thread-Index: AdoIEXz9ZtOM9jsoS4O3zul15JUS2QAALy6w
References: <20231024125416.798897-1-thomas@monjalon.net>
 <20231025163352.1076755-1-thomas@monjalon.net> <2170731.Icojqenx9y@thomas>
From: =?iso-8859-1?Q?Morten_Br=F8rup?= <mb@smartsharesystems.com>
To: "Thomas Monjalon" <thomas@monjalon.net>, <stephen@networkplumber.org>,
 <bruce.richardson@intel.com>
Cc: <dev@dpdk.org>,
	"David Marchand" <david.marchand@redhat.com>
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

> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Thursday, 26 October 2023 15.37
>=20
> 25/10/2023 18:31, Thomas Monjalon:
> > Real-time thread priority was been forbidden on Unix
> > because of problems they can cause.
> > Warnings and helpers are added to avoid deadlocks,
> > so real-time can be allowed on all systems.
>=20
> Unit test is failing:
> DPDK:fast-tests / threads_autotest      TIMEOUT 600.01 s
>=20
> It is seen in only 1 target (maybe the failure occurence is random):
>   Debian 11 (Buster) (ARM) | PASS
>   Fedora 37 (ARM)          | PASS
>   CentOS Stream 9 (ARM)    | FAIL
>   Fedora 38 (ARM)          | PASS
>   Fedora 38 (ARM Clang)    | PASS
>   Ubuntu 20.04 (ARM)       | PASS
>=20
> I need to send a v4 with new implementation and better comments.
> The Unix sleep will be upgraded from 1 ns to 1 us in case it makes a
> difference.

It will not make a difference. The kernel will go through the sleeping =
steps, then wake up again and see the real-time thread is ready to run, =
and then immediately schedule it.

For testing purposes, consider sleeping 10 milliseconds or something =
significant like that.