[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6599ad830804030845m71d56d88u3508a252fc134ba5@mail.gmail.com>
Date: Thu, 3 Apr 2008 08:45:33 -0700
From: "Paul Menage" <menage@...gle.com>
To: "Balbir Singh" <balbir@...ux.vnet.ibm.com>
Cc: "Pavel Emelianov" <xemul@...nvz.org>,
"Hugh Dickins" <hugh@...itas.com>,
"Sudhir Kumar" <skumar@...ux.vnet.ibm.com>,
"YAMAMOTO Takashi" <yamamoto@...inux.co.jp>, lizf@...fujitsu.com,
linux-kernel@...r.kernel.org, taka@...inux.co.jp,
linux-mm@...ck.org, "David Rientjes" <rientjes@...gle.com>,
"Andrew Morton" <akpm@...ux-foundation.org>,
"KAMEZAWA Hiroyuki" <kamezawa.hiroyu@...fujitsu.com>
Subject: Re: [-mm] Add an owner to the mm_struct (v6)
On Thu, Apr 3, 2008 at 12:30 AM, Balbir Singh <balbir@...ux.vnet.ibm.com> wrote:
> + This option enables mm_struct's to have an owner. The advantage
> + of this approach is that it allows for several independent memory
> + based cgorup controllers to co-exist independently without too
cgorup -> cgroup
> + if (need_mm_owner_callback) {
> + int i;
> + for (i = 0; i < CGROUP_SUBSYS_COUNT; i++) {
> + struct cgroup_subsys *ss = subsys[i];
> + oldcgrp = task_cgroup(old, ss->subsys_id);
> + newcgrp = task_cgroup(new, ss->subsys_id);
> + if (oldcgrp == newcgrp)
> + continue;
> + if (ss->mm_owner_changed)
> + ss->mm_owner_changed(ss, oldcgrp, newcgrp);
Even better, maybe just pass in the relevant cgroup_subsys_state
objects here, rather than the cgroup objects?
>
> css_get(&mem->css);
> - rcu_assign_pointer(mm->mem_cgroup, mem);
> css_put(&old_mem->css);
These get/put calls are now unwanted?
Could you also add comments in mm_need_new_owner(), in particular the
reason for checking for delay_group_leader() ?
Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists