From: Ramakrishnan Muthukrishnan <vu3rdd@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] [GSOC] plan9 kernel scheduler
Date: Mon, 23 Jun 2014 21:36:00 +0530 [thread overview]
Message-ID: <CAA6Yd9WRZYH0dXsRFKEMqt30RWqZmzWxPh_Dz0B5tY_3B6VBQA@mail.gmail.com> (raw)
In-Reply-To: <65984946d00c8ebe35122418a4f83cb1@mikro.quanstro.net>
On Sun, Jun 22, 2014 at 5:40 PM, erik quanstrom <quanstro@quanstro.net> wrote:
> On Sat Jun 21 21:47:37 EDT 2014, jyu@cowsay.org wrote:
>> +1 what Yoann said. :-) On SMP systems, all maches share a global run
>> queue, and maches tend to try grabbing procs that have run on it
>> before (affinity). Take a look at port/proc.c in particular, where a
>> lot of the scheduling logic is implemented.
>
> the (base) plan 9 scheduler uses a global priority based round robin
> scheduler. priority is absolute; a process of priority n+1
> will always run before a process of priority n. processes within
> a priority are run in round-robin fashion. recent cpu usage lowers
> a processes' priority. there is soft affinity that tends to rerun a
> process on the same cpu when practical, though this mechanism is
> too hard inthe standard distribution. there is hard affinity; one can
> wire a proc to a mach.
>
> a key detail of the scheduler is the set of priorities with runnable
> processes is kept in a bitvector named "runvec". significantly less
> than 32 priorities are used.
>
> there is also an edf scheduler. i can't find the iwp9 paper atm.
Is it this one?
"Lightweight EDF Scheduling with Deadline
Inheritance" by Jansen, S.J.Mullender et al.
<http://doc.utwente.nl/41399/1/000000c6.pdf>
next prev parent reply other threads:[~2014-06-23 16:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-21 19:30 yan cui
2014-06-22 1:10 ` Yoann Padioleau
2014-06-22 1:45 ` Jessica Yu
2014-06-22 12:10 ` erik quanstrom
2014-06-23 16:06 ` Ramakrishnan Muthukrishnan [this message]
2014-06-23 16:30 ` erik quanstrom
2014-06-23 18:37 ` andrey mirtchovski
2014-06-24 1:33 ` Ramakrishnan Muthukrishnan
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=CAA6Yd9WRZYH0dXsRFKEMqt30RWqZmzWxPh_Dz0B5tY_3B6VBQA@mail.gmail.com \
--to=vu3rdd@gmail.com \
--cc=9fans@9fans.net \
/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).