Re: [PATCH 0/5] IO-less dirty throttling v8
From: Vivek Goyal
Date: Thu Aug 11 2011 - 17:00:35 EST
On Thu, Aug 11, 2011 at 04:42:55PM -0400, Vivek Goyal wrote:
> So I see following immediate extension of your scheme possible.
> - Inherit ioprio from iocontext and provide buffered write service
> differentiation for writers.
> - Create a per task buffered write throttling interface and do
> absolute throttling of task.
> - We can possibly do the idea of throttling group wide buffered
> writes only control at this layer using this mechanism.
Though personally I like the idea of absolute throttling at page cache
level as it can help a bit with problem of buffered WRITES impacting
the latency of everything else in the system. CFQ helps a lot but
it idles enough that cost of this isolation is very high on faster
Deadline and noop really do not do much about protection from WRITEs.
So it is not perfect but might prove to be good enough for some use
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/