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
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
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
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.
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
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,
6 matches
Mail list logo
