Developers identify tasks and the library maps them to kernel threads

When a thread makes a blocking system call, another thread can run

OS creates a set of kernel threads (less than or equal to user threads)

When a thread makes a blocking system call, another thread can run

OS creates a kernel thread per user thread (can burden performance)

The entire process will block if a thread makes a blocking system call

Thread management is done in user space by a thread library not OS

Only one user thread can access the kernel at a time

The server creates a thread for each request

The thread is discarded once it has completed its work

Helps developing modern applications with hundreds of threads

Programmers identify tasks that can run in parallel

The programmer writes a task as a function

Too many threads that work concurrently can exhaust system resources

In explicit threading The number of threads that can be created has no upper bound.

in implicit threading Programmers identify threads

Run-time libraries (not programmers) create and manage threads

works well for tasks that are synchronous (cooperating).

works well for asynchronous (independent) tasks

in implicit threading Each task is mapped to a separate thread using the many-to-many model

At startup, the server creates a set of threads in a pool