memcg: kill CONFIG_MM_OWNER

CONFIG_MM_OWNER makes no sense.  It is not user-selectable, it is only
selected by CONFIG_MEMCG automatically.  So we can kill this option in
init/Kconfig and do s/CONFIG_MM_OWNER/CONFIG_MEMCG/ globally.

Signed-off-by: Oleg Nesterov <oleg@redhat.com>
Acked-by: Michal Hocko <mhocko@suse.cz>
Acked-by: Johannes Weiner <hannes@cmpxchg.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

1 files changed, 0 insertions, 7 deletions

diff --git a/init/Kconfig b/init/Kconfig
index 4a1822a1a680..0a2f09a80e90 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -933,7 +933,6 @@ config RESOURCE_COUNTERS
 config MEMCG
         bool "Memory Resource Controller for Control Groups"
         depends on RESOURCE_COUNTERS
-        select MM_OWNER
         select EVENTFD
         help
           Provides a memory resource controller that manages both anonymous
@@ -951,9 +950,6 @@ config MEMCG
           disable memory resource controller and you can avoid overheads.
           (and lose benefits of memory resource controller)
 
-          This config option also selects MM_OWNER config option, which
-          could in turn add some fork/exit overhead.
-
 config MEMCG_SWAP
         bool "Memory Resource Controller Swap Extension"
         depends on MEMCG && SWAP
@@ -1179,9 +1175,6 @@ config SCHED_AUTOGROUP
           desktop applications.  Task group autogeneration is currently based
           upon task session.
 
-config MM_OWNER
-        bool
-
 config SYSFS_DEPRECATED
         bool "Enable deprecated sysfs features to support old userspace tools"
         depends on SYSFS