From: Mike Galbraith <efault@gmx.de>
To: jim.houston@attbi.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] self tuning scheduler
Date: Wed, 12 Mar 2003 06:19:16 +0100 [thread overview]
Message-ID: <5.2.0.9.2.20030312060926.00cfc920@pop.gmx.net> (raw)
In-Reply-To: <3E6E6B81.4E7CD256@attbi.com>
At 06:04 PM 3/11/2003 -0500, Jim Houston wrote:
>Hi Mike
>
>I made a bit of progress on understanding the irman problem with
>my scheduler change. When I run irman and top, the processes end
>up with priorities like:
>
> irman parent 36
> irman child 21
> process_child 31-33 (group of 9 processes)
>
>Since I expanded the range of priorities (to 0-79) these are quite
>favorable priorities. They are all have MAX_SLEEP_AVG bonus
>equivelent of nice +10.
>
>It's a priority inversion problem. The irman child is waiting for
>a read. The process_child processes are happly running as a group
>at approximately the same priority. The irman parent is starved
>because it is at a lower priority. It is at a lower priority because
>it uses more cpu on each pass. It is doing the gettimeofday calls
>while the child only does the pipe read & write. The parent gets
>an occasional boost from the fairness_update() code so it doesn't
>totally starve.
I forgot to mention something odd I encountered wrt the parent's
priority. I can set the irman child SCHED_RR, and it shows up in top with
priority -2. The parent remains at priority 36 and remains starved. Max
renice doesn't help either.
-Mike
next prev parent reply other threads:[~2003-03-12 5:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 23:04 Jim Houston
2003-03-12 4:51 ` Mike Galbraith
2003-03-12 5:19 ` Mike Galbraith [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-11 0:30 Jim Houston
2003-03-11 9:46 ` Mike Galbraith
2003-03-11 19:05 ` Jim Houston
2003-03-11 20:09 ` Mike Galbraith
2003-03-11 19:17 ` Mike Galbraith
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=5.2.0.9.2.20030312060926.00cfc920@pop.gmx.net \
--to=efault@gmx.de \
--cc=jim.houston@attbi.com \
--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
all inboxes | Powered by JetHome®