a. User level threads
- glibc approach (one user thread per operation ?)
poor scalability, performance
Glibc uses a pool of threads, not one thread per operation.
All requests against a single file descriptor are served sequentially,
while for different fds they are served by different threads unless aio
thread limit has been reached, in which case they are queued too.
b. Pool of threads
- have a pool of threads servicing an aio request queue for the
task - tradeof between degree of concurrency/utilization and
resource consumption.
Jakub
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/