lkml.org 
[lkml]   [2008]   [May]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC][PATCH 0/2] memcg: simple hierarchy (v2)
On Fri, 30 May 2008 10:43:12 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:

> Implemented Policy:
> - parent overcommits all children
> parent->usage = resource used by itself + resource moved to children.
> Of course, parent->limit > parent->usage.
> - when child's limit is set, the resouce moves.
> - no automatic resource moving between parent <-> child

> Why this is enough ?
> - A middleware can do various kind of resource balancing only by reseting "limit"
> in userland.

I like this idea. The alternative could mean having a page live
on multiple cgroup LRU lists, not just the zone LRU and the one
cgroup LRU, and drastically increasing run time overhead.

Swapping memory in and out is horrendously slow anyway, so the
idea of having a daemon adjust the limits on the fly should work
just fine.

--
All rights reversed.


\
 
 \ /
  Last update: 2008-05-30 03:51    [W:0.076 / U:0.112 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site