Hello, Greg. On Wed, Feb 11, 2015 at 10:28:44AM -0800, Greg Thelen wrote: > This seems good. I assume that blkcg writeback would query > corresponding memcg for dirty page count to determine if over > background limit. And balance_dirty_pages() would query memcg's dirty Yeah, available memory to the matching memcg and the number of dirty pages in it. It's gonna work the same way as the global case just scoped to the cgroup. > page count to throttle based on blkcg's bandwidth. Note: memcg > doesn't yet have dirty page counts, but several of us have made > attempts at adding the counters. And it shouldn't be hard to get them > merged. Can you please post those? So, cool, we're in agreement. Working on it. It shouldn't take too long, hopefully. Thanks. -- tejun -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>