alleryStart learning →In the many-to-one user-to-kernel thread mapping, a single blocking I/O call
Ablocks all the user threads in the process
Bblocks only the calling user thread; others run normally
Cis forbidden by the OS
Dautomatically switches to a different process
Answer & Solution
Correct answer: A. blocks all the user threads in the process
In many-to-one (M:1), the user-space library multiplexes many user threads onto ONE kernel thread.
The OS only sees that single kernel thread.
When it blocks on a syscall, the kernel parks it
all the user threads sharing it are stuck too.
This is why M:1 is rare in production
one-to-one (Linux pthreads) avoids the issue at the cost of more kernel-side overhead.
Keep practising Operating Systems
Browse all Operating Systems questions for GATE CSE, or explore more Computer Science topics.
Related questions
On a MULTI-CORE system, a SPIN LOCK is generallyA LIVELOCK differs from a DEADLOCK in thatSuppose thread A acquires lock L1, then thread B acquires lock L2. Now A tries to acquire A CRITICAL SECTION isA LOCK is considered FAIR ifA LOCK (mutex) is used by concurrent threads toWhich of the following is NOT typically minimised by a CPU scheduler?The PRIMARY DISADVANTAGE of FIFO scheduling is