[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070828083252.C7D5C1BFA2F@siro.lan>
Date: Tue, 28 Aug 2007 17:32:52 +0900 (JST)
From: yamamoto@...inux.co.jp (YAMAMOTO Takashi)
To: balbir@...ux.vnet.ibm.com
Cc: akpm@...ux-foundation.org, npiggin@...e.de, a.p.zijlstra@...llo.nl,
dhaval@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, ebiederm@...ssion.com,
containers@...ts.osdl.org, menage@...gle.com, xemul@...nvz.org
Subject: Re: [-mm PATCH 5/10] Memory controller task migration (v7)
> YAMAMOTO Takashi wrote:
> >> Allow tasks to migrate from one container to the other. We migrate
> >> mm_struct's mem_container only when the thread group id migrates.
> >
> >> + /*
> >> + * Only thread group leaders are allowed to migrate, the mm_struct is
> >> + * in effect owned by the leader
> >> + */
> >> + if (p->tgid != p->pid)
> >> + goto out;
> >
> > does it mean that you can't move a process between containers
> > once its thread group leader exited?
> >
> > YAMAMOTO Takashi
>
>
> Hi,
>
> Good catch! Currently, we treat the mm as owned by the thread group leader.
> But this policy can be easily adapted to any other desired policy.
> Would you like to see it change to something else?
>
> --
> Warm Regards,
> Balbir Singh
> Linux Technology Center
> IBM, ISTL
although i have no good idea right now, something which allows
to move a process with its thread group leader dead would be better.
YAMAMOTO Takashi
-
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