Re: [PATCH v2 11/29] cgroups: ability to stop res charge propagationon bounded ancestor
From: KAMEZAWA Hiroyuki
Date: Mon May 14 2012 - 23:02:39 EST
(2012/05/12 2:44), Glauber Costa wrote:
> From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
> Moving a task from a cgroup to another may require to substract its
> resource charge from the old cgroup and add it to the new one.
> For this to happen, the uncharge/charge propagation can just stop when we
> reach the common ancestor for the two cgroups. Further the performance
> reasons, we also want to avoid to temporarily overload the common
> ancestors with a non-accurate resource counter usage if we charge first
> the new cgroup and uncharge the old one thereafter. This is going to be a
> requirement for the coming max number of task subsystem.
> To solve this, provide a pair of new API that can charge/uncharge a
> resource counter until we reach a given ancestor.
> Signed-off-by: Frederic Weisbecker <fweisbec@xxxxxxxxx>
> Acked-by: Paul Menage <paul@xxxxxxxxxxxxxx>
> Acked-by: Glauber Costa <glommer@xxxxxxxxxxxxx>
> Cc: Li Zefan <lizf@xxxxxxxxxxxxxx>
> Cc: Johannes Weiner <hannes@xxxxxxxxxxx>
> Cc: Aditya Kali <adityakali@xxxxxxxxxx>
> Cc: Oleg Nesterov <oleg@xxxxxxxxxx>
> Cc: Kay Sievers <kay.sievers@xxxxxxxx>
> Cc: Tim Hockin <thockin@xxxxxxxxxx>
> Cc: Tejun Heo <htejun@xxxxxxxxx>
> Acked-by: Kirill A. Shutemov <kirill@xxxxxxxxxxxxx>
> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Where is this function called in this series ?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/