All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Hillf Danton <dhillf@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Steven Rostedt <rostedt@goodmis.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 15:47:16 +0200	[thread overview]
Message-ID: <1306244836.2497.60.camel@laptop> (raw)
In-Reply-To: <BANLkTinrHfVT43Evto3GqN8venDrLXoMbg@mail.gmail.com>

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.

-ENOPARSE.. 

> 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:/ 

Starvation of the same priority tasks is a perfectly valid situation for
SCHED_FIFO, also, your changelog fails to mention what you propose to do
about it.


  parent reply	other threads:[~2011-05-24 13:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24 13:34 [PATCH] sched: remove starvation in check_preempt_equal_prio() Hillf Danton
2011-05-24 13:45 ` Steven Rostedt
2011-05-24 14:11   ` Hillf Danton
2011-05-24 14:22     ` Steven Rostedt
2011-05-24 13:47 ` Peter Zijlstra [this message]
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=1306244836.2497.60.camel@laptop \
    --to=peterz@infradead.org \
    --cc=dhillf@gmail.com \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.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 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.