Question

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

Answer 1

All models maps user-level threads to kernel-level threads. A kernel thread is similar to a process in a non-threaded (single-threaded) system. The kernel thread is the unit of execution that is scheduled by the kernel to execute on the CPU. The term virtual processor is often used instead of kernel thread.

That is what is typically done. Most modern platforms don't really have user threads anymore. You will find two technologies that are similar to user threads, coroutines, and strands/fibers. But they're not pre-emptive. So real user threading has pretty much died out in favor of kernel threads

Each thread belongs to exactly one process and no thread can exist outside a process, In multiple processing environments, each process executes the same ... and the corresponding Kernel threads can run in parallel on a multiprocessor