From: Rick Hohensee <humbubba@smarty.smart.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] commercial deployment
Date: Thu, 26 Jul 2001 10:01:25 -0400 [thread overview]
Message-ID: <200107261401.KAA07263@smarty.smart.net> (raw)
In-Reply-To: <20010726115552.9FB7619A10@mail.cse.psu.edu> from "rob pike" at Jul 26, 2001 07:55:50 AM
>
> This is a multi-part message in MIME format.
> --upas-odkgklfjzdotnlpxfzoohjyzvb
> Content-Disposition: inline
> Content-Type: text/plain; charset="US-ASCII"
> Content-Transfer-Encoding: 7bit
>
> > hmm, right, the same way "priority inheritence protocols" (Sha et al.)
> > for the priority inversion problem is "academic." :-]
>
> An academic solution to an academic problem. Ever notice that Plan 9
> has process priorities that influence scheduling, but interrupts are
> either on (spllo) or off (splhi)? That simplification, which was a
> step I took when I wrote the very first version of the kernel, fixed a
> problem I didn't even know existed at the time. Another blow struck
> in the fight for simplicity.
>
> -rob
>
Fight the good fight!
Rick Hohensee
next prev parent reply other threads:[~2001-07-26 14:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-26 11:55 rob pike
2001-07-26 13:23 ` Boyd Roberts
2001-07-26 14:01 ` Rick Hohensee [this message]
2001-07-26 15:38 ` Ozan Yigit
-- strict thread matches above, loose matches on Subject: below --
2001-07-21 17:32 bwc
2001-07-20 14:20 bwc
2001-07-21 9:53 ` Steve Kilbane
2001-07-19 19:28 anothy
2001-07-19 20:36 ` Mike Haertel
2001-07-19 22:34 ` Fariborz 'Skip' Tavakkolian
2001-07-20 8:59 ` Alberto Nava
2001-07-20 16:47 ` Ozan Yigit
2001-07-20 21:52 ` Rick Hohensee
2001-07-24 11:34 ` Ozan Yigit
2001-07-25 1:40 ` Rick Hohensee
2001-07-25 3:52 ` Boyd Roberts
2001-07-26 8:48 ` Ozan Yigit
2001-07-20 21:56 ` Boyd Roberts
2001-07-19 8:24 Stephen King
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=200107261401.KAA07263@smarty.smart.net \
--to=humbubba@smarty.smart.net \
--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).