linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
Cc: menage@google.com, xemul@openvz.org, hugh@veritas.com,
	skumar@linux.vnet.ibm.com, yamamoto@valinux.co.jp,
	lizf@cn.fujitsu.com, linux-kernel@vger.kernel.org,
	taka@valinux.co.jp, linux-mm@kvack.org, rientjes@google.com,
	balbir@linux.vnet.ibm.com, kamezawa.hiroyu@jp.fujitsu.com
Subject: Re: [-mm] Add an owner to the mm_struct (v8)
Date: Mon, 7 Apr 2008 15:09:56 -0700	[thread overview]
Message-ID: <20080407150956.9a29573a.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080404080544.26313.38199.sendpatchset@localhost.localdomain>

On Fri, 04 Apr 2008 13:35:44 +0530
Balbir Singh <balbir@linux.vnet.ibm.com> wrote:

> 1. Add mm->owner change callbacks using cgroups
> 
> ...
>
> +config MM_OWNER
> +	bool "Enable ownership of mm structure"
> +	help
> +	  This option enables mm_struct's to have an owner. The advantage
> +	  of this approach is that it allows for several independent memory
> +	  based cgroup controllers to co-exist independently without too
> +	  much space overhead
> +
> +	  This feature adds fork/exit overhead. So enable this only if
> +	  you need resource controllers

Do we really want to offer this option to people?  It's rather a low-level
thing and it's likely to cause more confusion than it's worth.  Remember
that most kernels get to our users via kernel vendors - to what will they
be setting this config option?

>  config CGROUP_MEM_RES_CTLR
>  	bool "Memory Resource Controller for Control Groups"
>  	depends on CGROUPS && RESOURCE_COUNTERS
> +	select MM_OWNER

Presumably they'll always be setting it to "y" if they are enabling cgroups
at all.

> --- linux-2.6.25-rc8/kernel/cgroup.c~memory-controller-add-mm-owner	2008-04-03 22:43:27.000000000 +0530
> +++ linux-2.6.25-rc8-balbir/kernel/cgroup.c	2008-04-03 22:43:27.000000000 +0530
> @@ -118,6 +118,7 @@ static int root_count;
>   * be called.
>   */
>  static int need_forkexit_callback;
> +static int need_mm_owner_callback;

I suppose these should be __read_mostly.

  parent reply	other threads:[~2008-04-07 22:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-04  8:05 Balbir Singh
2008-04-04  8:12 ` Paul Menage
2008-04-04  8:28   ` Balbir Singh
2008-04-04  8:50     ` Paul Menage
2008-04-04  9:25       ` Balbir Singh
2008-04-04 19:11         ` Paul Menage
2008-04-05 14:47           ` Balbir Singh
2008-04-05 17:23             ` Paul Menage
2008-04-05 17:48               ` Balbir Singh
2008-04-05 17:57                 ` Paul Menage
2008-04-05 18:59                   ` Balbir Singh
2008-04-05 23:29                     ` Paul Menage
2008-04-06  5:38                       ` Balbir Singh
2008-04-08  6:37                         ` Paul Menage
2008-04-08  6:52                           ` Balbir Singh
2008-04-08  6:57                             ` Paul Menage
2008-04-08  7:05                               ` Balbir Singh
2008-04-08  7:29                                 ` Paul Menage
2008-04-10  9:09                                   ` Balbir Singh
2008-04-05 23:31                     ` Paul Menage
2008-04-06  6:31                       ` Balbir Singh
2008-04-08  6:32                         ` Paul Menage
2008-04-07 22:09 ` Andrew Morton [this message]
2008-04-08  2:39   ` Balbir Singh
2008-04-08  2:55     ` Andrew Morton
2008-04-09  0:42 ` KAMEZAWA Hiroyuki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080407150956.9a29573a.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=hugh@veritas.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=menage@google.com \
    --cc=rientjes@google.com \
    --cc=skumar@linux.vnet.ibm.com \
    --cc=taka@valinux.co.jp \
    --cc=xemul@openvz.org \
    --cc=yamamoto@valinux.co.jp \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox