Which statement is true about the difference between user-level and kernel-level threads, and the benefits of multithreading?

• A. User-level threads are managed in user space, while kernel-level threads are managed by the operating system.
• B. Kernel threads are managed entirely by the GPUs.
• C. User-level threads cannot run concurrently.
• D. There is no difference in performance between the two.

Answer: (A)

Understanding how threads are managed helps explain why multithreading can improve a program’s behavior. User-level threads are created and scheduled by a library inside the application’s own address space; the operating system kernel does not manage these threads directly. Kernel-level threads are created, scheduled, and managed by the OS kernel, which can assign them to real hardware processors. This distinction matters for performance and parallelism: switching between user-level threads is fast because it doesn’t require a system call, but the OS may not be able to run multiple user-level threads in parallel if it doesn’t see them as separate kernel threads. Kernel threads allow true parallel execution on multiple cores since the OS can schedule different threads on different CPUs. Multithreading brings benefits like better responsiveness and higher CPU utilization by overlapping computation with I/O and by organizing work into concurrent tasks.

So, the statement that user-level threads are managed in user space while kernel-level threads are managed by the operating system captures the essential difference. The other options misstate aspects about GPUs, concurrent execution of user-level threads, or performance equivalence.