Path: utzoo!utgpu!water!watmath!clyde!att!mtunx!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!pasteur!ucbvax!decwrl!purdue!i.cc.purdue.edu!j.cc.purdue.edu!pur-ee!uiucdcs!uxc.cso.uiuc.edu!urbsdc!aglew From: aglew@urbsdc.Urbana.Gould.COM Newsgroups: comp.unix.questions Subject: Re: Real-time UNIX - what is it & who h Message-ID: <29500026@urbsdc> Date: 25 Jun 88 02:40:00 GMT References: <649@necis.UUCP> Lines: 27 Nf-ID: #R:necis.UUCP:649:urbsdc:29500026:000:1343 Nf-From: urbsdc.Urbana.Gould.COM!aglew Jun 24 21:40:00 1988 >Is there anything else we're missing? I don't think so. However, I'd love >to hear what other people think. We're not saying that there aren't other >features that wouldn't be nice to have, but the heart of "real-time"-hood >comes down to scheduling. Sure, I agree - all the other Real Time features are just there to provide support for the scheduler. Fast I/O, prepaging... Of course, the fact that I did our RT scheduler, and that I love all types of scheduling problems, might colour my attitude a little bit... Ahh, scheduling: time sharing, fair-sharing, fixed priority, deadline driven, feasibility... it's wonderful stuff! By the way, has anyone commercially implemented a deadline driven scheduler? And, can anyone who has worked on (preferably managed) an AT&T system with the fair share scheduler share their experiences with me (by mail, address below)? Andy "Krazy" Glew. Gould CSD-Urbana. 1101 E. University, Urbana, IL 61801 aglew@gould.com - preferred, if you have MX records aglew@xenurus.gould.com - if you don't ...!ihnp4!uiucuxc!ccvaxa!aglew - paths may still be the only way My opinions are my own, and are not the opinions of my employer, or any other organisation. I indicate my company only so that the reader may account for any possible bias I may have towards our products.