Hi, > TODO: > > * Try to push down the throttling and implement it directly in the I/O > schedulers, using bio-cgroup (http://people.valinux.co.jp/~ryov/bio-cgroup/) > to keep track of the right cgroup context. This approach could lead to more > memory consumption and increases the number of dirty pages (hard/slow to > reclaim pages) in the system, since dirty-page ratio in memory is not > limited. This could even lead to potential OOM conditions, but these problems > can be resolved directly into the memory cgroup subsystem > > * Handle I/O generated by kswapd: at the moment there's no control on the I/O > generated by kswapd; try to use the page_cgroup functionality of the memory > cgroup controller to track this kind of I/O and charge the right cgroup when > pages are swapped in/out FYI, this also can be done with bio-cgroup, which determine the owner cgroup of a given anonymous page. Thanks, Hirokazu Takahashi _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
