From: Peter Zijlstra <peterz@infradead.org>
To: Tommaso Cucinotta <tommaso.cucinotta@sssup.it>
Cc: Dhaval Giani <dhaval.giani@gmail.com>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Dario Faggioli <faggioli@gandalf.sssup.it>,
Fabio Checconi <fabio@gandalf.sssup.it>,
linux-kernel@vger.kernel.org
Subject: Re: 1 RT task blocks 4-core machine ?
Date: Wed, 06 Oct 2010 15:34:05 +0200 [thread overview]
Message-ID: <1286372045.2144.180.camel@laptop> (raw)
In-Reply-To: <4CAA54A1.6050507@sssup.it>
On Tue, 2010-10-05 at 00:26 +0200, Tommaso Cucinotta wrote:
> A possible explanation might be that the CFS load balancing logic sees
> my only active task (e.g., the ssh server or shell etc.) as running
> alone on its core, and does not detect that it is inhibited to actually
> run due to RT tasks on the same core. Therefore, it will not migrate
> the task to the free cores. Does this explanation make sense
> or is it completely wrong ?
Possibly, its got some logic to detect this but maybe it gets confused
still, in particular look at the adaptive cpu_power in
update_cpu_power() and calling functions.
> Also, I'd like to hear whether this is considered the "normal/desired"
> behavior of intermixing RT and non-RT tasks.
Pegging a cpu using sched_fifo/rr pretty much means you get to keep the
pieces, if it works nice, if you can make it work better kudos, but no
polling from sched_fifo/rr is not something that is considered sane for
the general health of your system.
next prev parent reply other threads:[~2010-10-06 13:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTim2icGqFWB1S6TVcQwmo+sCcGdNDPO3s8LFqzR=@mail.gmail.com>
2010-10-04 22:26 ` 1 RT task blocks 4-core machine ? Tommaso Cucinotta
2010-10-06 13:34 ` Peter Zijlstra [this message]
2010-10-09 17:42 Tommaso Cucinotta
2010-10-11 7:53 ` 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=1286372045.2144.180.camel@laptop \
--to=peterz@infradead.org \
--cc=dhaval.giani@gmail.com \
--cc=fabio@gandalf.sssup.it \
--cc=faggioli@gandalf.sssup.it \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=tommaso.cucinotta@sssup.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.