From: mikpe@csd.uu.se
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: [patch] 2.4.21-pre5 correct scheduling of idle tasks [ all arch ]
Date: Thu, 27 Mar 2003 16:54:47 +0100 [thread overview]
Message-ID: <16003.7879.340300.737153@gargle.gargle.HOWL> (raw)
In-Reply-To: <31961.1048659043@kao2.melbourne.sgi.com>
Keith Owens writes:
> There are several inconsistencies in the scheduling of idle tasks and,
> for UP, tracking which task is on the cpu. This patch standardizes
> idle task scheduling across all architectures and corrects the UP
> error, it is just a bug fix.
...
> To make it worse, on UP a task is assigned to a cpu but never released.
> Very quickly, all tasks are marked as currently running on cpu 0 :(.
->cpus_runnable and task_has_cpu() are SMP-only, as a quick grep
through 2.4.20 will tell you. There is no UP bug here to fix.
/Mikael
next prev parent reply other threads:[~2003-03-27 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 6:10 Keith Owens
2003-03-27 15:54 ` mikpe [this message]
2003-03-27 22:17 ` Keith Owens
2003-03-28 10:10 ` mikpe
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=16003.7879.340300.737153@gargle.gargle.HOWL \
--to=mikpe@csd.uu.se \
--cc=kaos@ocs.com.au \
--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
all inboxes | Powered by JetHome®