[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200125111931.GW11457@worktop.programming.kicks-ass.net>
Date: Sat, 25 Jan 2020 12:19:31 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Alex Kogan <alex.kogan@...cle.com>
Cc: Waiman Long <longman@...hat.com>, linux@...linux.org.uk,
Ingo Molnar <mingo@...hat.com>,
Will Deacon <will.deacon@....com>,
Arnd Bergmann <arnd@...db.de>, linux-arch@...r.kernel.org,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Borislav Petkov <bp@...en8.de>, hpa@...or.com, x86@...nel.org,
Hanjun Guo <guohanjun@...wei.com>,
Jan Glauber <jglauber@...vell.com>,
Steven Sistare <steven.sistare@...cle.com>,
Daniel Jordan <daniel.m.jordan@...cle.com>,
dave.dice@...cle.com
Subject: Re: [PATCH v8 4/5] locking/qspinlock: Introduce starvation avoidance
into CNA
On Fri, Jan 24, 2020 at 01:19:05PM -0500, Alex Kogan wrote:
> Is there a lightweight way to identify such a “prioritized” thread?
No; people might for instance care about tail latencies between their
identically spec'ed worker tasks.
In general it turns out that priority is a dynamic concept, not a static
one.
Powered by blists - more mailing lists