Re: [PATCH] memcg: Provide knob for force OOM into the memcg

2014-12-19 Thread Johannes Weiner
On Wed, Dec 17, 2014 at 05:41:29PM +0530, Chintan Pandya wrote: > > >Why do you move tasks around during runtime? Rather than scanning > >thousands or millions of page table entries to relocate a task and its > >private memory to another configuration domain, wouldn't it be easier to > >just keep

Re: [PATCH] memcg: Provide knob for force OOM into the memcg

2014-12-17 Thread Chintan Pandya
Why do you move tasks around during runtime? Rather than scanning thousands or millions of page table entries to relocate a task and its private memory to another configuration domain, wouldn't it be easier to just keep the task in a dedicated cgroup and reconfigure that instead? Your suggest

Re: [PATCH] memcg: Provide knob for force OOM into the memcg

2014-12-17 Thread Chintan Pandya
On 12/17/2014 04:03 AM, David Rientjes wrote: On Tue, 16 Dec 2014, Michal Hocko wrote: We may want to use memcg to limit the total memory footprint of all the processes within the one group. This may lead to a situation where any arbitrary process cannot get migrated to that one memcg because

Re: [PATCH] memcg: Provide knob for force OOM into the memcg

2014-12-16 Thread David Rientjes
On Tue, 16 Dec 2014, Michal Hocko wrote: > > We may want to use memcg to limit the total memory > > footprint of all the processes within the one group. > > This may lead to a situation where any arbitrary > > process cannot get migrated to that one memcg > > because its limits will be breached.

Re: [PATCH] memcg: Provide knob for force OOM into the memcg

2014-12-16 Thread Johannes Weiner
On Tue, Dec 16, 2014 at 06:55:35PM +0530, Chintan Pandya wrote: > We may want to use memcg to limit the total memory > footprint of all the processes within the one group. > This may lead to a situation where any arbitrary > process cannot get migrated to that one memcg > because its limits will b

Re: [PATCH] memcg: Provide knob for force OOM into the memcg

2014-12-16 Thread Michal Hocko
On Tue 16-12-14 18:55:35, Chintan Pandya wrote: > We may want to use memcg to limit the total memory > footprint of all the processes within the one group. > This may lead to a situation where any arbitrary > process cannot get migrated to that one memcg > because its limits will be breached. Or,

[PATCH] memcg: Provide knob for force OOM into the memcg

2014-12-16 Thread Chintan Pandya
We may want to use memcg to limit the total memory footprint of all the processes within the one group. This may lead to a situation where any arbitrary process cannot get migrated to that one memcg because its limits will be breached. Or, process can get migrated but even being most recently used