From: "Paul Menage" <menage@google.com>
To: YAMAMOTO Takashi <yamamoto@valinux.co.jp>
Cc: balbir@linux.vnet.ibm.com, xemul@openvz.org, hugh@veritas.com,
skumar@linux.vnet.ibm.com, lizf@cn.fujitsu.com,
linux-kernel@vger.kernel.org, taka@valinux.co.jp,
linux-mm@kvack.org, rientjes@google.com,
akpm@linux-foundation.org, kamezawa.hiroyu@jp.fujitsu.com
Subject: Re: [RFC][-mm] Add an owner to the mm_struct (v3)
Date: Mon, 31 Mar 2008 23:06:12 -0700 [thread overview]
Message-ID: <6599ad830803312306l59fabaa0o2f62feb0d59b2ce3@mail.gmail.com> (raw)
In-Reply-To: <20080401060330.743815A02@siro.lan>
On Mon, Mar 31, 2008 at 11:03 PM, YAMAMOTO Takashi
<yamamoto@valinux.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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-04-01 6:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 5:43 Balbir Singh
2008-04-01 6:03 ` YAMAMOTO Takashi
2008-04-01 6:06 ` Paul Menage [this message]
2008-04-01 6:24 ` YAMAMOTO Takashi
2008-04-01 6:25 ` Balbir Singh
2008-04-01 6:16 ` Paul Menage
2008-04-01 6:23 ` Balbir Singh
2008-04-01 6:48 ` Paul Menage
2008-04-01 7:26 ` Balbir Singh
2008-04-01 8:13 ` Balbir Singh
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=6599ad830803312306l59fabaa0o2f62feb0d59b2ce3@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