| |||||||||||||
KS2010: Deadline schedulingKS2010: Deadline schedulingPosted Nov 8, 2010 1:47 UTC (Mon) by vonbrand (subscriber, #4458)In reply to: KS2010: Deadline scheduling by tcucinotta Parent article: KS2010: Deadline scheduling
That might work for soft real time (whatever that means), for the "multiton machine that could kill you in an instant" application mentioned above this is very far from acceptable. "Real time" is a system property (kernel with all its areas, computer on which it runs, and application code). Trying to fix that scheduling the CPU alone is certainly bullshit.
(Log in to post comments)
KS2010: Deadline scheduling Posted Nov 8, 2010 20:40 UTC (Mon) by tcucinotta (guest, #69261) [Link] I agree absolutely with all the statements. However, I also think we should undertake an incremental approach, otherwise we end-up with nothing. For this round, we're discussing about how to improve CPU scheduling. This is only one of the essential bricks that are needed in order to support real-time applications and increase predictability of software. Of course, a comprehensive approach to the problem needs to consider other resources as well, like networking and disk transfers, as well as the IRQ subsystem architecture. Still, improving CPU scheduling is just a little step that is strongly needed, has a relevant impact on the problem, and it can be done without subverting the way scheduling and resource management is handled inside the kernel.
|
|||||||||||||