From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Rostedt Subject: Re: [PATCH] sched/rt: RT_RUNTIME_GREED sched feature Date: Mon, 7 Nov 2016 15:00:03 -0500 Message-ID: <20161107150003.66777b43@gandalf.local.home> References: <20161107133207.4282de69@gandalf.local.home> <20161107144738.4811a5dd@gandalf.local.home> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Daniel Bristot de Oliveira , Ingo Molnar , Peter Zijlstra , linux-rt-users , LKML To: Christoph Lameter Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-rt-users.vger.kernel.org On Mon, 7 Nov 2016 13:54:12 -0600 (CST) Christoph Lameter wrote: > On Mon, 7 Nov 2016, Steven Rostedt wrote: > > > On Mon, 7 Nov 2016 13:30:15 -0600 (CST) > > Christoph Lameter wrote: > > > > > SCHED_RR tasks alternately running on on cpu can cause endless deferral of > > > kworker threads. With the global effect of the OS processing reserved > > > it may be the case that the processor we are executing never gets any > > > time. And if that kworker threads role is releasing a mutex (like the > > > cgroup_lock) then deadlocks can result. > > > > I believe SCHED_RR tasks will still throttle if they use up too much of > > the CPU. But I still don't see how this patch helps your situation. > > The kworker thread will be able to make progress? Or am I not reading this > correctly? > If kworker is SCHED_OTHER, then it will be able to make progress if the RT tasks are throttled. What Daniel's patch does, is to turn off throttling of the RT tasks if there's no other task on the run queue. -- Steve