> > take a look at rw_swap_page(). If served with wait==1, it does wait for
> > swapout to finish. When a process is sleeping there, it _is_ waiting for
> > kswapd too (kswapd is probably busy trying to free some pages as well).
>
> Uhmm, no. If a process is sleeping there, it's probably because
> it's doing the I/O in it's _own_ context.
i didnt mean it literally, i ment it in a more abstract way. If a process
has to swapout a page, then probably kswapd is running too, because memory
is tight. Otherwise the direct coupling between 'no memory for process X'
and 'kswapd' is pretty loose, and done through swap_tick(), which is
pretty much unsuitable to carry any RT-priority ...
-- mingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu