From: Jim Houston <jim.houston@ccur.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Jim Houston <jim.houston@attbi.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: O(1) Scheduler (tuning problem/live-lock)
Date: Tue, 01 Oct 2002 03:20:57 -0400 [thread overview]
Message-ID: <3D994CD9.3FDFA09F@ccur.com> (raw)
In-Reply-To: 20020930161019.GH1235@dualathlon.random
Hi Andrea, Ingo,
Andrea I tried your patch and it does solve the live-lock
in the LTP waitpid06 test. The mouse movement gets a bit
jerky but atleast it doesn't lock up.
I guess the next question is how does it do on normal work loads?
I like the idea of making the child processes start with a smaller
sleep_avg value. Maybe it should just be a constant rather than a
fraction of the parents sleep_avg? Its really the child processes
inheriting the favorable sleep_avg that caused the problem with
waitpid06.
I liked the idea of giving interactive tasks special treatment.
Andrea please don't remove this. Always putting processes
(which have used up there time slice) into the rq->expired array
makes all processes round robin at the same priority. It makes
sense to do this to fail gracefully if the system is overloaded
but not all the time.
I hope this make sense. I'm falling asleep writing it:-)
Jim Houston - Concurrent Computer Corp.
next prev parent reply other threads:[~2002-10-01 7:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-06 18:44 O(1) Scheduler (tuning problem/live-lock) Jim Houston
2002-09-30 16:10 ` Andrea Arcangeli
2002-10-01 7:20 ` Jim Houston [this message]
2002-10-02 6:45 ` Andrea Arcangeli
2002-10-03 5:50 ` Jim Houston
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=3D994CD9.3FDFA09F@ccur.com \
--to=jim.houston@ccur.com \
--cc=andrea@suse.de \
--cc=jim.houston@attbi.com \
--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 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).