On Tue, Apr 21, 2009 at 10:30:02AM +0200, Andrea Righi wrote: > > We're trying to address also this issue, setting max dirty pages limit > per cgroup, and force a direct writeback when these limits are exceeded. > > In this case dirty ratio throttling should happen automatically because > the process will be throttled by the IO controller when it tries to > writeback the dirty pages and submit IO requests. The challenge here will be the accounting; consider that you may have a file that had some of its pages in its page cache dirtied by a process in cgroup A. Now another process in cgroup B dirties some more pages. This could happen either via a mmap'ed file or via the standard read/write system calls. How do you track which dirty pages should be charged against which cgroup? - Ted _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
