From: Lightweight patch manager <patch@luckynet.dynu.com>
To: Robert Love <rml@tech9.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: [PATCH][2.5] make kernel scheduler use list_move_tail (1 occ)
Date: Sun, 9 Jun 2002 08:22:06 -0600 (MDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0206090820100.25737-100000@hawkeye.luckynet.adm> (raw)
This makes the kernel scheduler use list_move_tail instead of more code
--- linus-2.5/kernel/sched.c Sun Jun 9 04:17:27 2002
+++ thunder-2.5/kernel/sched.c Sun Jun 9 06:58:51 2002
@@ -1360,8 +1360,7 @@
* then just requeue the task to the end of the runqueue:
*/
if (likely(current->prio == MAX_PRIO-1 || rt_task(current))) {
- list_del(¤t->run_list);
- list_add_tail(¤t->run_list, array->queue + current->prio);
+ list_move_tail(¤t->run_list, array->queue + current->prio);
} else {
list_del(¤t->run_list);
if (list_empty(array->queue + current->prio))
--
Lightweight patch manager using pine. If you have any objections, tell me.
next reply other threads:[~2002-06-09 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-09 14:22 Lightweight patch manager [this message]
2002-06-09 17:22 ` [PATCH][2.5] make kernel scheduler use list_move_tail (1 occ) Robert Love
2002-06-09 17:26 ` Robert Love
2002-06-09 17:49 ` Thunder from the hill
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.44.0206090820100.25737-100000@hawkeye.luckynet.adm \
--to=patch@luckynet.dynu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rml@tech9.net \
/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;
as well as URLs for NNTP newsgroup(s).