We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Consider 20 tasks ( Ti,T2….T20) having same priority level and consider time slice duration as 10usecond. Now when Task1 get switched to process Task2 then in how much time Task1 will get resumed.
That depends on the functionality of other tasks - do they wait? give up their time slice? lock a mutex? etc. etc. etc.
@Tamir,
Thanks for the reply, If it doesn't wait, or doesn't lock lock mutex etc.. what is the time slice for task switch.
If so, and using round-robin scheduling, you can expect your task to run every "nr. of tasks * time slice duratrion" time units.
Thanks a lot.
Note that 10us is a very short time slice period.
For every processor type and for every OS, there will be a need to consume a specific number of instructin cycles for performing a task switch.
This time will come out of the time slice period since the new task will not be able to run until the OS is done with the task switch.
With too short time slice perids, all CPU time will go to the task switching and your tasks will not get anything done.
@Per Westermark,
Thanks a lot for pointing out important point!!!