mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Hillf Danton <dhillf@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Peter Zijlstra <peterz@infradead.org>,
	Mike Galbraith <efault@gmx.de>,
	Yong Zhang <yong.zhang0@gmail.com>
Subject: Re: [PATCH] sched: remove starvation in check_preempt_equal_prio()
Date: Tue, 24 May 2011 10:22:33 -0400	[thread overview]
Message-ID: <1306246953.1465.64.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <BANLkTim0RtCjefq5Z2qbJFbBhrCHFfeGxg@mail.gmail.com>

On Tue, 2011-05-24 at 22:11 +0800, Hillf Danton wrote:
> On Tue, May 24, 2011 at 9:45 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
> > On Tue, 2011-05-24 at 21:34 +0800, Hillf Danton wrote:
> >> If there are pushable tasks and they are high enough in priority, in which
> >> case task p is covered, the current could keep holding its CPU.
> >>
> >> Even if current task has to release its CPU, requeuing task p could result in
> >> starvation of tasks that are of same priority and have been waiting on RQ for
> >> a couple of hours:/
> >
> > Can you explain this better? Sounds like you are describing the
> > definition of FIFO. You are *not* suppose to preempt a FIFO task just
> 
> I dont want to redefine FIFO, but starvation needs attention, since
> the woken task is already off RQ, and its position on RQ is reshuffled.

Does this happen because your other patch doesn't do the work at wake up
anymore? That is, you require a schedule of the high prio task?

There should be no starvation if the currently woken RT task can
migrate, as it should simply go to another rq.

-- Steve



  reply	other threads:[~2011-05-24 14:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24 13:34 Hillf Danton
2011-05-24 13:45 ` Steven Rostedt
2011-05-24 14:11   ` Hillf Danton
2011-05-24 14:22     ` Steven Rostedt [this message]
2011-05-24 13:47 ` Peter Zijlstra
2011-05-24 14:01   ` Hillf Danton
2011-05-24 14:24     ` Steven Rostedt
2011-05-24 14:33       ` Hillf Danton
2011-05-24 14:46         ` Steven Rostedt
2011-05-24 15:04           ` Hillf Danton
2011-05-25 14:00           ` Hillf Danton
2011-05-25 14:13             ` Steven Rostedt

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=1306246953.1465.64.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=dhillf@gmail.com \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=yong.zhang0@gmail.com \
    /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®