From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,2a4e090733b9f44e X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-06-23 16:24:29 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!cyclone.bc.net!tdsnet-transit!newspeer.tds.net!news.binc.net!kilgallen From: Kilgallen@SpamCop.net (Larry Kilgallen) Newsgroups: comp.lang.ada Subject: Re: Task execution time (writing a scheduler) Date: 23 Jun 2003 18:24:26 -0500 Organization: LJK Software Message-ID: References: NNTP-Posting-Host: eisner.encompasserve.org X-Trace: grandcanyon.binc.net 1056410641 19073 192.135.80.34 (23 Jun 2003 23:24:01 GMT) X-Complaints-To: abuse@binc.net NNTP-Posting-Date: Mon, 23 Jun 2003 23:24:01 +0000 (UTC) Xref: archiver1.google.com comp.lang.ada:39625 Date: 2003-06-23T18:24:26-05:00 List-Id: In article , Ole Kristensen writes: > Kilgallen@SpamCop.net (Larry Kilgallen) writes: > > > >> To communicate better, you should explain what you mean by EDF. > > Earliest deadline first. Well, that rule would certainly make for a rather simplistic scheduler, allowing a task with an early deadline to fully lock out other tasks with intermittant CPU needs to miss their deadline because the first of their IO operations (which automatically yield the CPU) were not allowed to start until the early deadline task finished.