mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Galbraith <bitbucket@online.de>
To: Chuansheng Liu <chuansheng.liu@intel.com>
Cc: mingo@kernel.org, peterz@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: sched/rt: Pick up the throttled rt tasks in case no other non-rt tasks
Date: Wed, 16 Oct 2013 08:56:41 +0200	[thread overview]
Message-ID: <1381906601.5472.62.camel@marge.simpson.net> (raw)
In-Reply-To: <1381938216.26153.63.camel@cliu38-desktop-build>

On Wed, 2013-10-16 at 23:43 +0800, Chuansheng Liu wrote: 
> Meet the case that on CPU2, there are just two tasks to be run,
> one is one rt task A, another is idle task, but at this time,
> and the rt_rq is throttled.
> 
> CPU1		                 CPU2
> 				 staying in idle task;
> waking up rt task A on
> target CPU 2;
> 
>                                  exiting from idle task;
>                                  DO schedule()
>                                    pick up RT next task
> 					pick_next_task_rt()
> 						_pick_next_task_rt()
> 						rt_rq is throttled
> 					return NULL rt task to be picked
> 
> 				 CPU2 then went into idle task AGAIN;
>                                  after 2s, CPU2 is waken up again;
>                                  rt task A is get running;
> 
> Here rt task A is delayed for some time, even when CPU2 is in idle state.
> 
> so in case there are just rt tasks running, we can pick up one of them
> even rt_rq is throttled.

And shortly thereafter, a SCHED_NORMAL task wakes.. only to find that
its alleged bodyguard slit its throat while it slept.  Bad bodyguard.

-Mike


      reply	other threads:[~2013-10-16  6:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-16 15:43 Chuansheng Liu
2013-10-16  6:56 ` Mike Galbraith [this message]

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=1381906601.5472.62.camel@marge.simpson.net \
    --to=bitbucket@online.de \
    --cc=chuansheng.liu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.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

all inboxes | Powered by JetHome®