public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Roland Dreier <roland@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: runnable tasks never making it to a runqueue where they can run?
Date: Wed, 07 Mar 2012 17:30:23 +0100	[thread overview]
Message-ID: <1331137823.11248.353.camel@twins> (raw)
In-Reply-To: <CAL1RGDUbxcx+cCM_mf1nFJ=Jz0SyaiW0ffxiY4gZ6KNWzJCnMg@mail.gmail.com>

On Tue, 2012-03-06 at 18:19 -0800, Roland Dreier wrote:
> Is this expected behavior? 

Its not unexpected.. although I had hoped we'd not suck quite as bad.

The 'idea' is that scale_rt_power() will decrease the cpu_power of cpus
that run RT tasks and the rest of the load-balancing will then dtrt.

Clearly its not quite working.

>  I can believe that we brought this on ourselves by
> misconfiguring things, but in that case it would be good to know what we could
> do to avoid this problem. 

hard-affine everything.. eg. create a system cpuset and only give it
cpu23 (although cpu0 would be more typical) and run only a single task
on every other cpu.

Once you do that, it doesn't really matter if your one task is FIFO or
not, with the exception that system tasks (like ksoftirqd, kworker/n
etc..) can still run when required.

Running FIFO spinners is known to break stuff due to those system tasks
not getting run. Fixing this is somewhat non-trivial :/

Alternatively you can of course play with stuff like commit 4a6184ce



  reply	other threads:[~2012-03-07 16:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-07  2:19 runnable tasks never making it to a runqueue where they can run? Roland Dreier
2012-03-07 16:30 ` Peter Zijlstra [this message]
2012-03-07 16:31 ` Peter Zijlstra
2012-03-07 18:03   ` Roland Dreier
2012-03-08 10:28     ` Peter Zijlstra
2012-03-08 11:55       ` Srivatsa Vaddagiri
2012-03-08 12:00         ` Peter Zijlstra

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1331137823.11248.353.camel@twins \
    --to=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox