Sistem terbenam: Perbedaan antara revisi

Konten dihapus Konten ditambahkan
Gunarto adam (bicara | kontrib)
kTidak ada ringkasan suntingan
Baris 206:
Take the above nonpreemptive task system, and run it from a preemptive timer or other interrupts.
 
Suddenly the system is quite different. Any piece of task code can damage the data of another task—theytask-they must be precisely separated. Access to shared data must be rigidly controlled by some synchronization strategy, for example message queues or semaphores. (Recently [[non-blocking synchronization]] strategies have been developed).
 
Often, at this stage, the developing organization buys a [[real-time operating system]]. This can be a wise decision if the organization lacks people with the skills to write one, or if the port of the operating system to the hardware will be used in several products. Otherwise, be aware that it usually adds six to eight weeks to the schedule, and forever after programmers can blame delays on it.