Re: mogstored (and cmogstored) threads per device

[Eric Wong <e@80x24.org>]

dormando <dormando@rydia.net> wrote:
> Wonder if you could autotune it a bit? Start with a low default, then
> self-increase if the threads are starved too often. Self-tuning would
> disable if started at something other than the default or if 'SERVER
> aio_threads = XX' were issued

I've thought of autotuning, but then reliably detecting starvation in
userspace might be more trouble than it's worth (and expensive).
Probably the best way to leave things unchanged: give the kernel as
much work as possible and let the kernel scheduler decide what to do
with it.

Threads (even with 20K stack) are still pretty cheap and epoll interacts
well with the scheduler: extra/excess threads never get woken due to
FIFO ordering of threads in epoll_wait.