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 776DCA0556;
	Fri, 27 May 2022 13:15:06 +0200 (CEST)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 5FB5D40E78;
	Fri, 27 May 2022 13:15:06 +0200 (CEST)
Received: from linux.microsoft.com (linux.microsoft.com [13.77.154.182])
 by mails.dpdk.org (Postfix) with ESMTP id 75AB840E5A
 for <dev@dpdk.org>; Fri, 27 May 2022 13:15:05 +0200 (CEST)
Received: by linux.microsoft.com (Postfix, from userid 1086)
 id C1E8520B895B; Fri, 27 May 2022 04:15:04 -0700 (PDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com C1E8520B895B
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com;
 s=default; t=1653650104;
 bh=GNyXHPlflZdyz6a2CXj4SNjGdhsbxJ/buenZFv2zEco=;
 h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
 b=WUEXRFDUzhsccxvN811BXFNK6Ft2ButpP/daZ8V7CklPs7TWVEpxi1ci7hVhanKgB
 dDXi3PhLS9j8l7kfCJlA+Br2tWxDl8LY+gRgWLqtKJeFHkE42Vn+ngORHzu9BNNywg
 PrkohbR3Kxm1hr5/7+t6phnKEJGJ71Rwsdh+EaP8=
Date: Fri, 27 May 2022 04:15:04 -0700
From: Tyler Retzlaff <roretzla@linux.microsoft.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, thomas@monjalon.net, dmitry.kozliuk@gmail.com,
 anatoly.burakov@intel.com, Narcisa Vasile <navasile@linux.microsoft.com>
Subject: Re: [PATCH v3 1/2] eal: get/set thread priority per thread identifier
Message-ID: <20220527111504.GA20461@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
References: <1653302773-11043-1-git-send-email-roretzla@linux.microsoft.com>
 <1653390517-4033-1-git-send-email-roretzla@linux.microsoft.com>
 <1653390517-4033-2-git-send-email-roretzla@linux.microsoft.com>
 <20220524075105.01713e7d@hermes.local>
 <20220526062957.GA27713@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
 <20220526082127.023edfc3@hermes.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20220526082127.023edfc3@hermes.local>
User-Agent: Mutt/1.5.21 (2010-09-15)
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

On Thu, May 26, 2022 at 08:21:27AM -0700, Stephen Hemminger wrote:
> 
> Thanks for clarifying.
> Is there any analog for SCHED_DEADLINE worth considering?

i hadn't considered it. for now i probably won't since this patch is
just a blocker for getting the thread lifetime series up. which is
higher priority as i understand.