Hey, Vivek. On Wed, Apr 04, 2012 at 11:49:09AM -0700, Tejun Heo wrote: > > I am not sure what are you trying to say here. But primarily blk-throttle > > will throttle read and direct IO. Buffered writes will go to root cgroup > > which is typically unthrottled. > > Ooh, my bad then. Anyways, then the same applies to blk-throttle. > Our current implementation essentially collapses at the face of > write-heavy workload. I went through the code and couldn't find where blk-throttle is discriminating async IOs. Were you saying that blk-throttle currently doesn't throttle because those IOs aren't associated with the dirtying task? If so, note that it's different from cfq which explicitly assigns all async IOs when choosing cfqq even if we fix tagging. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
