Re: [PATCH] cgroups: don't depend on CONFIG_MM_OWNER

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Pekka J Enberg <penberg@...>
Cc: <akpm@...>, <linux-kernel@...>, <balbir@...>
Date: Monday, September 15, 2008 - 1:55 pm

On Sun, Sep 14, 2008 at 10:37 AM, Pekka J Enberg <penberg@cs.helsinki.fi> wrote:

Yes, the existing code doesn't seem quite right - if !CONFIG_MM_OWNER
then we don't need to even define a trivial version of
cgroup_mm_owner_callbacks()

But your patch is too specific - tying the existance of
cgroup_mm_owner_callbacks() to the memory controller would break other
controllers (e.g. the memrlimit or swap controllers, which also want
to use it)

How about:

- any cgroup that needs mm-owner callbacks selects an option
CGROUP_MM_OWNER_CALLBACK

- CGROUP_MM_OWNER_CALLBACK selects MM_OWNER and triggers the
definition of a non-trivial cgroup_mm_owner_callbacks() function


Paul


--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH] cgroups: don't depend on CONFIG_MM_OWNER, Pekka J Enberg, (Sun Sep 14, 1:37 pm)
Re: [PATCH] cgroups: don't depend on CONFIG_MM_OWNER, Paul Menage, (Mon Sep 15, 1:55 pm)
Re: [PATCH] cgroups: don't depend on CONFIG_MM_OWNER, Pekka Enberg, (Mon Sep 15, 1:56 pm)