From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] priority bug
Date: Thu, 28 Feb 2002 12:59:47 -0500 [thread overview]
Message-ID: <e6a6ec035bc02a27184eb1887044f851@plan9.bell-labs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 702 bytes --]
It worked but was a bit too major to stick in the normal
release. It knew about oversubscribing and would relegate
anything that didn't have the focus to best effort.
It had the advantage of being able to have many things
going and the one you were most interested in to have
all the resource it wanted. It scheduled not only cpu
but other resources as well.
At one point I started sticking it into the main line
but the related changes were a little too pervasive
for me so I backed out.
Now we have a real time scheduler that pb(peter bosch)
did to handle mpeg streams and other goo. I haven't
used it but it is in our main stream so it'll at least
see the light of day someday.
[-- Attachment #2: Type: message/rfc822, Size: 1494 bytes --]
From: Scott Schwartz <schwartz@bio.cse.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] priority bug
Date: Thu, 28 Feb 2002 12:07:57 -0500
Message-ID: <20020228170757.2886.qmail@g.bio.cse.psu.edu>
A while back Eran Gabber had a usenix paper on an improved scheduler.
Did that work out well enough?
next reply other threads:[~2002-02-28 17:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 17:59 presotto [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-28 16:12 presotto
2002-02-28 17:07 ` Scott Schwartz
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=e6a6ec035bc02a27184eb1887044f851@plan9.bell-labs.com \
--to=presotto@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).