Question

5. Which of the methods used to map user threads to kernel threads can exploit a multiprocessor environment? Justify your answer.

Answer 1

In user-level thread the administration of thread are in library in user-level program. the TCB for multiple threads are put away at user-level and switch between the threads in same process are done in user-level library, every administration calls like - thread_create (), switch(), thread_destroy(), thread_yield(). these are dealt with by system brings in user-level thread. This model is executed inside the application and it contains no endeavor uphold from the kernel.

Every models maps user-level threads to kernel-level threads, a kernel thread is like a process in a non-threaded framework. The kernel thread is the unit of execution that is planned by the kernel to execute on the CPU. The term virtual processor is frequently utilized rather than kernel thread. That is what is normally done. Most present day platforms don't generally have user-threads any longer. You will discover two innovations that are like user-threads, co routines, and strands. In any case, they're not pre-emptive. So real user threading has essentially ceased to exist for kernel threads Each thread has a place with precisely one process and no thread can exist outside a process, in numerous processing conditions, each process executes the equivalent furthermore, the corresponding Kernel threads can run in equal on a multiprocessor

The presence to user-level thread is obscure to the kernel and it is overseen without kernel support and furthermore quicker to make than kernel level threads.