From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Serge E. Hallyn" Subject: Re: [RFC v14-rc3][PATCH 33/36] Support for share memory address spaces Date: Thu, 9 Apr 2009 19:09:27 -0500 Message-ID: <20090410000927.GA9912@us.ibm.com> References: <1239107264-21775-1-git-send-email-orenl@cs.columbia.edu> <1239107264-21775-34-git-send-email-orenl@cs.columbia.edu> <20090409210302.GA5115@us.ibm.com> <49DE72F7.9040001@cs.columbia.edu> <20090409225212.GA8386@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Oren Laadan Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, Dave Hansen List-Id: containers.vger.kernel.org Quoting Oren Laadan (orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org): > On Thu, 9 Apr 2009, Serge E. Hallyn wrote: > During task creation, the algorithm implies that the thread group > leader is created first, and it in turn clones all the other threads > in the thread group. > > So now they all share the same MM, and no other task shares that mm. > > One arbitrary thread is restarted first (depending on the checkpoint > order) - it will destory the VMAs in that MM and reconstruct new ones > within that MM. When other threads get to cr_read_mm() they will Oooh. I had it in my mind that a new mm was being created altogether. thanks, -serge