[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200422112719.826676174@infradead.org>
Date: Wed, 22 Apr 2020 13:27:19 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: mingo@...nel.org, linux-kernel@...r.kernel.org
Cc: tglx@...utronix.de, rostedt@...dmis.org, qais.yousef@....com,
juri.lelli@...hat.com, vincent.guittot@...aro.org,
dietmar.eggemann@....com, bsegall@...gle.com, mgorman@...e.de,
peterz@...radead.org
Subject: [PATCH 00/23] sched: Remove FIFO priorities from modules
After having seen yet another patch that adds a FIFO kernel thread at a random
priority, I bit the bullet and implemented the suggestion done a while ago:
Flat out remove the ability to set a specific FIFO priority
As argued in the patches themselves, the kernel has no clue what actual
priority it should use for various things, so it is useless (or worse, counter
productive) to even try.
Powered by blists - more mailing lists