From: Con Kolivas <kernel@kolivas.org>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>
Subject: [PATCH] 2.5.72 O(1) interactivity bugfix
Date: Thu, 19 Jun 2003 00:43:00 +1000 [thread overview]
Message-ID: <200306190043.14291.kernel@kolivas.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Ingo, all
While messing with the interactivity code I found what appears to be an
uninitialised variable (p->sleep_avg), which is responsible for all the
boost/penalty in the scheduler. Initialising this variable to 0 seems to have
made absolutely massive improvements to system responsiveness under load
and completely removed audio skips up to doing a make -j64 on my uniprocessor
P4 (beyond which swap starts being used), without changing the scheduler
timeslices. This seems to help all 2.4 O(1) based kernels as well. Attached
is a patch against 2.5.72 but I'm not sure about the best place to initialise
it.
diff -Naurp linux-2.5.72/kernel/fork.c linux-2.5.72-test/kernel/fork.c
- --- linux-2.5.72/kernel/fork.c 2003-06-18 22:47:25.000000000 +1000
+++ linux-2.5.72-test/kernel/fork.c 2003-06-19 00:30:26.000000000 +1000
@@ -864,6 +864,7 @@ struct task_struct *copy_process(unsigne
p->lock_depth = -1; /* -1 = no lock */
p->start_time = get_jiffies_64();
p->security = NULL;
+ p->sleep_avg = 0;
retval = -ENOMEM;
if ((retval = security_task_alloc(p)))
diff -Naurp linux-2.5.72/kernel/sched.c linux-2.5.72-test/kernel/sched.c
- --- linux-2.5.72/kernel/sched.c 2003-06-18 22:47:25.000000000 +1000
+++ linux-2.5.72-test/kernel/sched.c 2003-06-19 00:28:19.000000000 +1000
@@ -1755,6 +1755,7 @@ static int setscheduler(pid_t pid, int p
if (array)
deactivate_task(p, task_rq(p));
retval = 0;
+ p->sleep_avg = 0;
p->policy = policy;
p->rt_priority = lp.sched_priority;
if (policy != SCHED_NORMAL)
I hope this is correct.
Regards,
Con
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+8Hp0F6dfvkL3i1gRAr/fAKCYbJ/yQhshqV7G43f+mQP4rZoKWgCfdD69
QuqYH58q6PdbD3qGFvjUKSs=
=huFo
-----END PGP SIGNATURE-----
next reply other threads:[~2003-06-18 14:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 14:43 Con Kolivas [this message]
2003-06-18 17:59 ` [PATCH] 2.5.72 O(1) interactivity bugfix Andreas Boman
2003-06-18 22:43 ` Con Kolivas
[not found] ` <1055977195.1077.41.camel@asgaard.midgaard.us>
2003-06-18 23:38 ` Con Kolivas
[not found] ` <1055983621.1753.23.camel@asgaard.midgaard.us>
2003-06-19 1:12 ` Con Kolivas
2003-06-19 2:00 ` Andreas Boman
2003-06-19 6:13 ` Mike Galbraith
2003-06-19 6:35 ` Con Kolivas
2003-06-19 8:11 ` Con Kolivas
2003-06-19 7:33 ` Nick Piggin
2003-06-19 8:51 ` Mike Galbraith
2003-06-19 8:57 ` Nick Piggin
2003-06-19 9:00 ` Nick Piggin
2003-06-19 9:18 ` Mike Galbraith
2003-06-18 18:05 ` Robert Love
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=200306190043.14291.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.