From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: Con Kolivas <conman@kolivas.net>
Subject: Re: [BENCHMARK] scheduler tunables with contest - exit_weight
Date: Mon, 23 Dec 2002 01:49:01 +0100 [thread overview]
Message-ID: <200212230148.16806.m.c.p@wolk-project.de> (raw)
In-Reply-To: <200212220818.22906.conman@kolivas.net>
On Saturday 21 December 2002 22:18, Con Kolivas wrote:
Hey Con,
> osdl hardware, contest results, 2.5.52-mm2 with scheduler tunable - exit
> weight (ew1= exit weight ==1 and so on)
Can you please try another thing?
kernel/sched.c
/*
* If the child was a (relative-) CPU hog then decrease
* the sleep_avg of the parent as well.
*/
if (p->sleep_avg < p->parent->sleep_avg)
p->parent->sleep_avg = (p->parent->sleep_avg * exit_weight +
p->sleep_avg) / (exit_weight + 1);
Remove these please and run again.
ciao, Marc
next prev parent reply other threads:[~2002-12-23 0:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-21 21:18 [BENCHMARK] scheduler tunables with contest - exit_weight Con Kolivas
2002-12-23 0:49 ` Marc-Christian Petersen [this message]
2002-12-24 1:46 ` Con Kolivas
2002-12-25 13:24 ` Denis Vlasenko
2002-12-25 9:38 ` Con Kolivas
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=200212230148.16806.m.c.p@wolk-project.de \
--to=m.c.p@wolk-project.de \
--cc=conman@kolivas.net \
--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