From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: [sched] [patch] comment-fixes-2.5.3-pre2-A0
Date: Sun, 20 Jan 2002 14:13:53 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.33.0201201411230.7818-200000@localhost.localdomain> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 141 bytes --]
the attached patch from Rusty Russell fixes three comments in
kernel/sched.c. (I've updated it to apply cleanly against 2.5.3-pre2.)
Ingo
[-- Attachment #2: Type: TEXT/PLAIN, Size: 1249 bytes --]
--- linux/kernel/sched.c.orig Sun Jan 20 10:41:39 2002
+++ linux/kernel/sched.c Sun Jan 20 10:57:17 2002
@@ -37,11 +37,7 @@
*
* Locking rule: those places that want to lock multiple runqueues
* (such as the load balancing or the process migration code), lock
- * acquire operations must be ordered by the runqueue's cpu id.
- *
- * The RT event id is used to avoid calling into the the RT scheduler
- * if there is a RT task active in an SMP system but there is no
- * RT scheduling activity otherwise.
+ * acquire operations must be ordered by ascending &runqueue.
*/
struct runqueue {
spinlock_t lock;
@@ -538,7 +553,7 @@
* do not update a process's priority until it either
* goes to sleep or uses up its timeslice. This makes
* it possible for interactive tasks to use up their
- * timeslices at their high priority levels.
+ * timeslices at their highest priority levels.
*/
if (p->sleep_avg)
p->sleep_avg--;
@@ -853,7 +838,7 @@
if (array) {
enqueue_task(p, array);
/*
- * If the task is runnable and lowered its priority,
+ * If the task is running and lowered its priority,
* or increased its priority then reschedule its CPU:
*/
if ((nice < p->__nice) ||
reply other threads:[~2002-01-20 11:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.33.0201201411230.7818-200000@localhost.localdomain \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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®