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 3139D431A1; Wed, 25 Oct 2023 17:37:05 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9F040402B3; Wed, 25 Oct 2023 17:37:04 +0200 (CEST) Received: from mail-pf1-f178.google.com (mail-pf1-f178.google.com [209.85.210.178]) by mails.dpdk.org (Postfix) with ESMTP id 01B4F40273 for ; Wed, 25 Oct 2023 17:37:02 +0200 (CEST) Received: by mail-pf1-f178.google.com with SMTP id d2e1a72fcca58-6bee11456baso4875616b3a.1 for ; Wed, 25 Oct 2023 08:37:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1698248222; x=1698853022; darn=dpdk.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=ovCArtmZfeuqQ2F2AMFUVAYBH/2ETT8ZmxnuypQNiQ4=; b=BxCtf+wduPh7lOzUR4Vnb0fSpiMPf981Inc64/21mQckSs9coFsqR5HSXKU9swkxj/ dcSZNJVnlMwTNWwpZRztExf9Dbqc0jDyfvGd1QzhoFyZ8FUmLPDKYNSeMHq16ZW8+az6 aulyfv9acNWL2c4GPYJMo+qumdXu5qlRlha5Af+DvV/HVSNZLhYfREx5/IBBbEHUQNCS A4VKY4uFYX+bFCi1XkchHzEJCNv3ZZEBzpvWa7FsoQsjFUV3t2SJ5FLQWqOg7V3DsDaE Cdpi8/mH/Mk0WEjlZaU6VbNCHhjwJ7eijcdPvAF9QHZdeVBHIXXa37o9J+fJfTFXcQb/ 1Hiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698248222; x=1698853022; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=ovCArtmZfeuqQ2F2AMFUVAYBH/2ETT8ZmxnuypQNiQ4=; b=H6q23TkSOPzPoHzpzIBEvKJJqDiAF+2l9pTekxCcQVOd+vyVul6p4Gz1o9QY7K8C1w 3xx4vM3zDgJqrbnEwwMavgtKjerfyXscnFMA3pljK/SEZAWvIJSmF/F/0ElXZ1W5UJYx Y7saHv5KUGDNLIFGpmanOtBtPwnqX0+o6Duf79s0u4Pm8PafDQkfp5/a+44FT2MtwR3G kPUnKJaquPM5ZbEkekTCiWaSTo9E1pfIu9yH9g+JCFO6Sk4pZ1A3PViVNzr24HuNZguR mS1MpY30a1kU5bjBfxr4Re7fQPSQBPDWOmRWuZz8wljBDtktomnc2EfiCyJl/fVRmVVq mjEg== X-Gm-Message-State: AOJu0YzJIUe7KW9m7d7wuGgnLS2rQ0HAGis9Q1OBtuJ3Upf/lQ89nToE XOmniCEyStoYBHuOP1+7hvKrlg== X-Google-Smtp-Source: AGHT+IEUFnsyoIQKPCIb+24KX5zSj+8iiY7GCylI+lmIJnNvJXh3eLaXJDhPTzm+sIFhTglEtQiNlw== X-Received: by 2002:a05:6a21:339b:b0:17a:cfce:5a30 with SMTP id yy27-20020a056a21339b00b0017acfce5a30mr6719316pzb.16.1698248222071; Wed, 25 Oct 2023 08:37:02 -0700 (PDT) Received: from hermes.local (204-195-126-68.wavecable.com. [204.195.126.68]) by smtp.gmail.com with ESMTPSA id p66-20020a625b45000000b0068fe5a5a566sm10289552pfb.142.2023.10.25.08.37.01 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 25 Oct 2023 08:37:01 -0700 (PDT) Date: Wed, 25 Oct 2023 08:37:00 -0700 From: Stephen Hemminger To: Thomas Monjalon Cc: dev@dpdk.org, David Marchand , stable@dpdk.org, Morten =?UTF-8?B?QnLDuHJ1cA==?= , Anatoly Burakov , Dmitry Kozlyuk , Narcisa Ana Maria Vasile , Dmitry Malloy , Pallavi Kadam , Tyler Retzlaff , Andrew Rybchenko , Konstantin Ananyev Subject: Re: [PATCH v2] eal/unix: allow creating thread with real-time priority Message-ID: <20231025083700.4e3e274c@hermes.local> In-Reply-To: <20231025151352.995318-1-thomas@monjalon.net> References: <20231024125416.798897-1-thomas@monjalon.net> <20231025151352.995318-1-thomas@monjalon.net> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 On Wed, 25 Oct 2023 17:13:14 +0200 Thomas Monjalon wrote: > 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. > + */ I was thinking something like: static bool warned; if (!warned) { RTE_LOG(NOTICE, EAL, "Real time priority is unstable when thread is polling without sleep\n"); warned = true; }