[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6599ad830803312348u3ee4d815i2e24c130978f8e04@mail.gmail.com>
Date: Mon, 31 Mar 2008 23:48:00 -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 (v3)
On Mon, Mar 31, 2008 at 11:23 PM, Balbir Singh
<balbir@...ux.vnet.ibm.com> wrote:
> > Here we'll want to call vm_cgroup_update_mm_owner(), to adjust the
> > accounting. (Or if in future we end up with more than a couple of
> > subsystems that want notification at this time, we'll want to call
> > cgroup_update_mm_owner() and have it call any interested subsystems.
> >
>
> I don't think we need to adjust accounting, since only mm->owner is changing and
> not the cgroup to which the task/mm belongs. Do we really need to notify? I
> don't want to do any notifications under task_lock().
It's possible but unlikely that the new owner is in a different cgroup.
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