Talk:Fixed-priority pre-emptive scheduling: Difference between revisions

Revision as of 13:07, 27 August 2011

Revision as of 17:47, 26 May 2012

Line 2:

In my opinion it is wrong to ''say advantage of making sure no task hogs the processor for any time longer than the time slice''

fixed priority means only the highest priority thread will run.

:I agree; "priority" implies that you want some tasks to run first. You have to realize that trying to squeeze too many tasks into a r-t system can get you in trouble. A lot of papers have been written about how to guarantee that all critical tasks will always complete on time, but it may be more useful to advise practitioners to aim for no more than about 50% r-t utilization.

:A lot of designers try to cover problems by leaving interrupts off. This leads to systems which have potentially large interrupt latency and as a consequence a high variance in that value. Among other problems, this leads to systems that cannot guarantee effectively uniform sampling times, which violates one of the basic assumptions of most digital signal processing algorithms.

:--[[User:AJim|AJim]] ([[User talk:AJim|talk]]) 17:47, 26 May 2012 (UTC)

== advantages of this model ==