linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Paul Menage" <menage@google.com>
To: balbir@linux.vnet.ibm.com
Cc: Pavel Emelianov <xemul@openvz.org>,
	Hugh Dickins <hugh@veritas.com>,
	Sudhir Kumar <skumar@linux.vnet.ibm.com>,
	YAMAMOTO Takashi <yamamoto@valinux.co.jp>,
	lizf@cn.fujitsu.com, linux-kernel@vger.kernel.org,
	taka@valinux.co.jp, linux-mm@kvack.org,
	David Rientjes <rientjes@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [-mm] Add an owner to the mm_struct (v6)
Date: Thu, 3 Apr 2008 10:17:44 -0700	[thread overview]
Message-ID: <6599ad830804031017m60dc5ca5sebaa434e5bde8633@mail.gmail.com> (raw)
In-Reply-To: <47F5109D.8060606@linux.vnet.ibm.com>

On Thu, Apr 3, 2008 at 10:15 AM, Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
>  > Even better, maybe just pass in the relevant cgroup_subsys_state
>  > objects here, rather than the cgroup objects?
>  >
>
>  Is that better than passing the cgroups? All the callbacks I see usually pass
>  either task_struct or cgroup. Won't it be better, consistent use of API to pass
>  either of those?

I have a long term plan to try to divorce the subsystems from having
to worry too much about actual control groups where possible.

But I guess that for consistency with the current API, passing in the
cgroup is OK.

Paul

      reply	other threads:[~2008-04-03 17:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03  7:30 Balbir Singh
2008-04-03 15:45 ` Paul Menage
2008-04-03 17:15   ` Balbir Singh
2008-04-03 17:17     ` Paul Menage [this message]

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=6599ad830804031017m60dc5ca5sebaa434e5bde8633@mail.gmail.com \
    --to=menage@google.com \
    --cc=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=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