[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6599ad830804031130s666368a8v2b31ee6db493b501@mail.gmail.com>
Date: Thu, 3 Apr 2008 11:30:00 -0700
From: "Paul Menage" <menage@...gle.com>
To: "Dave Hansen" <dave@...ux.vnet.ibm.com>
Cc: "Balbir Singh" <balbir@...ux.vnet.ibm.com>,
"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: [-mm] Add an owner to the mm_struct (v7)
On Thu, Apr 3, 2008 at 11:25 AM, Dave Hansen <dave@...ux.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);
>
> What is the case in which we get here? Threading that's two deep where
> none of the immeidate siblings or children is still alive?
Probably the most likely case of this would be a LinuxThreads process
where the manager thread exits, and then the main thread, while other
threads still exist.
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