[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6599ad830803312306l59fabaa0o2f62feb0d59b2ce3@mail.gmail.com>
Date: Mon, 31 Mar 2008 23:06:12 -0700
From: "Paul Menage" <menage@...gle.com>
To: "YAMAMOTO Takashi" <yamamoto@...inux.co.jp>
Cc: balbir@...ux.vnet.ibm.com, xemul@...nvz.org, hugh@...itas.com,
skumar@...ux.vnet.ibm.com, lizf@...fujitsu.com,
linux-kernel@...r.kernel.org, taka@...inux.co.jp,
linux-mm@...ck.org, rientjes@...gle.com, akpm@...ux-foundation.org,
kamezawa.hiroyu@...fujitsu.com
Subject: Re: [RFC][-mm] Add an owner to the mm_struct (v3)
On Mon, Mar 31, 2008 at 11:03 PM, YAMAMOTO Takashi
<yamamoto@...inux.co.jp> wrote:
>
> changing mm->owner without notifying controllers makes it difficult to use.
> can you provide a notification mechanism?
>
Yes, I think that call will need to be in the task_lock() critical
section in which we update mm->owner.
Right now I think the only user that needs to be notified at that
point is Balbir's virtual address limits controller.
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