Anonymous user
Brendan's Multi-tasking Tutorial: Difference between revisions
m
→Step 4: Task States and "Schedule()" Version 2
| [unchecked revision] | [unchecked revision] |
Line 133:
==Step 4: Task States and "Schedule()" Version 2==
For a real OS (regardless of which scheduling algorithm/s the scheduler uses) most tasks switches are caused because the currently running task has to wait for something to happen (data received from a different task or storage devices/file system or network, or time
To prepare for this, we want to add some kind of "state" to each task so that it's easy to see what a task is doing (e.g. if it's waiting and what it's waiting for).
Line 158:
Note that if there's only one task you don't really want to do any task switches (because there's no other tasks to switch to), and in this case the task will be "running" and the list of "ready to run" tasks will be empty. The previous version of "schedule()" was a little less efficient (it would've done a task switch from one task to the same task).
==Step 5: Race Conditions and Locking Version 1==
| |||