From: "Paul Menage" <menage@google.com>
To: balbir@linux.vnet.ibm.com
Cc: Pavel Emelianov <xemul@openvz.org>,
Hugh Dickins <hugh@veritas.com>,
Sudhir Kumar <skumar@linux.vnet.ibm.com>,
YAMAMOTO Takashi <yamamoto@valinux.co.jp>,
linux-kernel@vger.kernel.org, taka@valinux.co.jp,
linux-mm@kvack.org, David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [-mm] Add an owner to the mm_struct (v8)
Date: Sat, 5 Apr 2008 16:29:35 -0700 [thread overview]
Message-ID: <6599ad830804051629k3649dbc4na92bb3d0cd7a0492@mail.gmail.com> (raw)
In-Reply-To: <47F7CC08.4090209@linux.vnet.ibm.com>
On Sat, Apr 5, 2008 at 11:59 AM, Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> > But surely the performance of thread exits wouldn't be affected by the
> > delay_group_leader(p) change, since none of the exiting threads would
> > be a group leader. That optimization only matters when the entire
> > process exits.
> >
>
> On the client side, each JVM instance exits after the test. I see the thread
> group leader exit as well through getdelays (I see TGID exits).
How long does the test run for? How many threads does each client have?
Paul
next prev parent reply other threads:[~2008-04-05 23:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 8:05 Balbir Singh
2008-04-04 8:12 ` Paul Menage
2008-04-04 8:28 ` Balbir Singh
2008-04-04 8:50 ` Paul Menage
2008-04-04 9:25 ` Balbir Singh
2008-04-04 19:11 ` Paul Menage
2008-04-05 14:47 ` Balbir Singh
2008-04-05 17:23 ` Paul Menage
2008-04-05 17:48 ` Balbir Singh
2008-04-05 17:57 ` Paul Menage
2008-04-05 18:59 ` Balbir Singh
2008-04-05 23:29 ` Paul Menage [this message]
2008-04-06 5:38 ` Balbir Singh
2008-04-08 6:37 ` Paul Menage
2008-04-08 6:52 ` Balbir Singh
2008-04-08 6:57 ` Paul Menage
2008-04-08 7:05 ` Balbir Singh
2008-04-08 7:29 ` Paul Menage
2008-04-10 9:09 ` Balbir Singh
2008-04-05 23:31 ` Paul Menage
2008-04-06 6:31 ` Balbir Singh
2008-04-08 6:32 ` Paul Menage
2008-04-07 22:09 ` Andrew Morton
2008-04-08 2:39 ` Balbir Singh
2008-04-08 2:55 ` Andrew Morton
2008-04-09 0:42 ` KAMEZAWA Hiroyuki
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=6599ad830804051629k3649dbc4na92bb3d0cd7a0492@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=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