From: Peter Williams <pwil3058@bigpond.net.au>
To: Paolo Ornati <ornati@fastwebnet.it>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Chris Han <xiphux@gmail.com>, Con Kolivas <kernel@kolivas.org>,
William Lee Irwin III <wli@holomorphy.com>,
Jake Moilanen <moilanen@austin.ibm.com>
Subject: Re: [ANNOUNCE][RFC] PlugSched-6.2 for 2.6.16-rc1 and 2.6.16-rc1-mm1
Date: Sun, 22 Jan 2006 10:06:43 +1100 [thread overview]
Message-ID: <43D2BE83.1020200@bigpond.net.au> (raw)
In-Reply-To: <20060121114616.4a906b4f@localhost>
Paolo Ornati wrote:
> On Fri, 20 Jan 2006 08:45:43 +1100
> Peter Williams <pwil3058@bigpond.net.au> wrote:
>
>
>>Modifications have been made to spa_ws to (hopefully) address the issues
>>raised by Paolo Ornati recently and a new entitlement based
>>interpretation of "nice" scheduler, spa_ebs, which is a cut down version
>>of the Zaphod schedulers "eb" mode has been added as this mode of Zaphod
>>performed will for Paolo's problem when he tried it at my request.
>>Paolo, could you please give these a test drive on your problem?
>
>
> ---- spa_ws: the problem is still here
>
> (sched_fooler)
> ./a.out 3000 & ./a.out 4307 &
>
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 5573 paolo 34 0 2396 292 228 R 59.0 0.1 0:24.51 a.out
> 5572 paolo 34 0 2392 288 228 R 40.7 0.1 0:16.94 a.out
> 5580 paolo 35 0 4948 1468 372 R 0.3 0.3 0:00.04 dd
>
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 5573 paolo 34 0 2396 292 228 R 59.3 0.1 0:59.65 a.out
> 5572 paolo 33 0 2392 288 228 R 40.3 0.1 0:41.32 a.out
> 5440 paolo 28 0 86652 21m 15m S 0.3 4.4 0:03.34 konsole
> 5580 paolo 37 0 4948 1468 372 R 0.3 0.3 0:00.10 dd
>
>
> (real life - transcode)
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 5585 paolo 33 0 115m 18m 2432 S 90.0 3.7 0:38.04 transcode
> 5599 paolo 37 0 50996 4472 1872 R 9.1 0.9 0:04.03 tcdecode
> 5610 paolo 37 0 4948 1468 372 R 0.6 0.3 0:00.19 dd
>
>
> DD test takes ages in both cases.
>
> What exactly have you done to spa_ws?
I added a "nice aware" version of the throughput bonuses from spa_svr
and renamed them fairness bonus. They don't appear to be working :-(
34 is the priority value that ordinary tasks should end up with i.e. if
they don't look like interactive tasks or CPU hogs. If they look like
interactive tasks they should get a lower one via the interactive bonus
mechanism and if they look like CPU hogs they should get a higher one
via the same mechanism. In addition to this tasks will get bonuses if
they seem to be being treated unfairly i.e. spending too much time on
run queues waiting for CPU access.
Looking at your numbers the transcode task has the priority that I'd
expect it to have but tcdecode and dd seem to have had their priorities
adjusted in the wrong direction. It's almost like they'd been
(incorrectly, obviously) identified as CPU hogs :-(. I'll look into this.
>
>
> ---- spa_ebs: great! (as expected)
>
> (sched_fooler)
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 5418 paolo 34 0 2392 288 228 R 51.4 0.1 1:06.47 a.out
> 5419 paolo 34 0 2392 288 228 R 43.7 0.1 0:54.60 a.out
> 5448 paolo 11 0 4952 1468 372 D 3.0 0.3 0:00.12 dd
>
> (transcode)
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 5456 paolo 34 0 115m 18m 2432 R 51.9 3.7 0:23.34 transcode
> 5470 paolo 12 0 51000 4472 1872 S 5.7 0.9 0:02.38 tcdecode
> 5480 paolo 11 0 4948 1468 372 D 3.5 0.3 0:00.33 dd
>
> Very good DD test performance in both cases.
Good. How do you find the interactive responsiveness with this one?
Thanks for testing
Peter
--
Peter Williams pwil3058@bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
next prev parent reply other threads:[~2006-01-21 23:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 21:45 [ANNOUNCE][RFC] PlugSched-6.2 for 2.6.16-rc1 and 2.6.16-rc1-mm1 Peter Williams
2006-01-21 6:48 ` Peter Williams
2006-01-21 10:46 ` Paolo Ornati
2006-01-21 23:06 ` Peter Williams [this message]
2006-01-22 22:47 ` Peter Williams
2006-01-23 0:49 ` Peter Williams
2006-01-23 20:21 ` Paolo Ornati
2006-01-24 0:00 ` Peter Williams
2006-01-26 1:09 ` Peter Williams
2006-01-26 8:11 ` Paolo Ornati
2006-01-26 22:34 ` Peter Williams
2006-01-28 23:44 ` Peter Williams
2006-01-31 17:44 ` Paolo Ornati
2006-01-23 20:09 ` Paolo Ornati
2006-01-23 20:25 ` Lee Revell
2006-01-23 20:52 ` Paolo Ornati
2006-01-23 20:59 ` Lee Revell
2006-01-23 21:10 ` Paolo Ornati
2006-01-23 21:11 ` Lee Revell
2006-01-23 23:32 ` Peter Williams
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=43D2BE83.1020200@bigpond.net.au \
--to=pwil3058@bigpond.net.au \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=moilanen@austin.ibm.com \
--cc=ornati@fastwebnet.it \
--cc=wli@holomorphy.com \
--cc=xiphux@gmail.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