public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Joe Korty <joe.korty@ccur.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6.3 Posix scheduling violation for !SCHED_OTHER
Date: Wed, 24 Mar 2004 01:01:21 +0100	[thread overview]
Message-ID: <20040324000121.GA2321@elte.hu> (raw)
In-Reply-To: <20040323233554.GA24010@tsunami.ccur.com>


* Joe Korty <joe.korty@ccur.com> wrote:

> Andrew,
>  The following fixes a problem where a SCHED_FIFO task would on
> occasion be moved to the end of its runqueue when returned to from a
> preemption. Cause was do to some SCHED_OTHER code in schedule() which
> was being run for tasks of every policy.

yes, indeed this is a bug.

> -	if (next->activated > 0) {
> +	if (!rt_task(next) && next->activated > 0) {

the patch looks good. Andrew, please apply.

	Ingo

      reply	other threads:[~2004-03-24  0:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-23 23:35 [PATCH] 2.6.3 Posix scheduling violation for !SCHED_OTHER Joe Korty
2004-03-24  0:01 ` Ingo Molnar [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=20040324000121.GA2321@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@osdl.org \
    --cc=joe.korty@ccur.com \
    --cc=linux-kernel@vger.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