Re: [RFC] Making memcg track ownership per address_space or anon_vma
From: Konstantin Khlebnikov
Date: Wed Feb 11 2015 - 16:22:41 EST
On Wed, Feb 11, 2015 at 11:33 PM, Tejun Heo <tj@xxxxxxxxxx> wrote:
> 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.
That might be a problem: all dirty pages accounted to cgroup must be
reachable for its own personal writeback or balanace-drity-pages will be
unable to satisfy memcg dirty memory thresholds. I've done accounting
for per-inode owner, but there is another option: shared inodes might be
handled differently and will be available for all (or related) cgroup
Another side is that reclaimer now (mosly?) never trigger pageout.
Memcg reclaimer should do something if it finds shared dirty page:
either move it into right cgroup or make that inode reachable for
memcg writeback. I've send patch which marks shared dirty inodes
with flag I_DIRTY_SHARED or so.
>> 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
> Can you please post those?
> So, cool, we're in agreement. Working on it. It shouldn't take too
> long, hopefully.
Good. As I see this design is almost equal to my proposal,
maybe except that dumb first-owns-all-until-the-end rule.
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@xxxxxxxxxx For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@xxxxxxxxx"> email@xxxxxxxxx </a>
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/