From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Paul Menage <menage@google.com>,
Pavel Emelianov <xemul@openvz.org>,
Hugh Dickins <hugh@veritas.com>,
Sudhir Kumar <skumar@linux.vnet.ibm.com>,
YAMAMOTO Takashi <yamamoto@valinux.co.jp>,
lizf@cn.fujitsu.com, linux-kernel@vger.kernel.org,
taka@valinux.co.jp, linux-mm@kvack.org,
David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC][-mm] Add an owner to the mm_struct (v4)
Date: Wed, 02 Apr 2008 12:10:43 +0530 [thread overview]
Message-ID: <47F32A6B.1070709@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080402135357.04c3e79f.kamezawa.hiroyu@jp.fujitsu.com>
KAMEZAWA Hiroyuki wrote:
> On Wed, 02 Apr 2008 08:55:34 +0530
> Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
>
>>>> + /*
>>>> + * Search through everything else. We should not get
>>>> + * here often
>>>> + */
>>>> + do_each_thread(g, c) {
>>>> + if (c->mm == mm)
>>>> + goto assign_new_owner;
>>>> + } while_each_thread(g, c);
>>> Doing above in synchronized manner seems too heavy.
>>> When this happen ? or Can this be done in lazy "on-demand" manner ?
>>>
>> Do you mean under task_lock()?
>>
> No, scanning itself.
> How rarely this scan happens under a server which has 10000- threads ?
>
This routine will be called every time a thread exits, but will quickly exit
after checking mm_need_new_owner()
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
next prev parent reply other threads:[~2008-04-02 6:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 12:43 Balbir Singh
2008-04-01 16:00 ` Pekka Enberg
2008-04-01 16:15 ` Balbir Singh
2008-04-02 0:31 ` KAMEZAWA Hiroyuki
2008-04-02 3:25 ` Balbir Singh
2008-04-02 4:53 ` KAMEZAWA Hiroyuki
2008-04-02 6:40 ` Balbir Singh [this message]
2008-04-02 19:27 ` Paul Menage
2008-04-02 18:53 ` Balbir Singh
2008-04-02 19:53 ` Paul Menage
2008-04-03 4:05 ` Balbir Singh
2008-04-03 4:10 ` Paul Menage
2008-04-03 4:32 ` 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=47F32A6B.1070709@linux.vnet.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--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=menage@google.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