[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6599ad830804022110h2090f3efg7c6173df8185679e@mail.gmail.com>
Date: Wed, 2 Apr 2008 21:10:36 -0700
From: "Paul Menage" <menage@...gle.com>
To: 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: [RFC][-mm] Add an owner to the mm_struct (v4)
On Wed, Apr 2, 2008 at 9:05 PM, Balbir Singh <balbir@...ux.vnet.ibm.com> wrote:
>
> I checked to see that cgroup_exit is called after mm_update_new_owner(). We call
> mm_update_new_owner() from exit_mm(). I did not check for current->cgroups !=
> new_owner->cgroups, since I did not want to limit the callbacks.
No cgroup subsystem should be concerned about mm ownership changes
between tasks in the same cgroup. So I think that's a valid and useful
optimization.
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