In: Electrical Engineering
Thread scheduling at the process level and at the kernel level. This topic requires more work on my part and I will give an updated draft. There may be more than one question here. Review the different allocation policies for kernel threads in relation to user threads – one to one, many to one, many to many, hybrid. These are sometimes referred to as an “M:N ratio” where M is the number of user threads and N is the number of kernel threads.
a) How is the choice between “process scope” (P) and“system scope” (S) related to these options? If “process scope” is chosen, where does the responsibility lie for scheduling threads?
b) How does Posix implement scheduling at the user thread level? If “system scope” (S) is chosen, does the programmer have any control over the scheduling of her threads?