Indeed, for write throttling we have to find another
solution. One thing we could do is set different
trottle targets for different processes.
(so process A is trottled at 10% dirty pages while
process B is trottled at 40% dirty pages ... with
priorities being recalculated once every second or
so to preserve fairness)
> And if you mean reads... Good luck propagating the originator
> information.
Isn't it the case that for most of the filesystem
reads the current process is the one that is the
originator of the request ?
regards,
Rik
--
"What you're running that piece of shit Gnome?!?!"
-- Miguel de Icaza, UKUUG 2000
http://www.conectiva.com/ http://www.surriel.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/