From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: [RFC v13][PATCH 00/14] Kernel based checkpoint/restart Date: Thu, 12 Feb 2009 11:42:07 -0800 Message-ID: <20090212114207.e1c2de82.akpm@linux-foundation.org> References: <1233076092-8660-1-git-send-email-orenl@cs.columbia.edu> <1234285547.30155.6.camel@nimitz> <20090211141434.dfa1d079.akpm@linux-foundation.org> <1234462282.30155.171.camel@nimitz> <1234467035.3243.538.camel@calx> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1234467035.3243.538.camel@calx> Sender: owner-linux-mm@kvack.org To: Matt Mackall Cc: dave@linux.vnet.ibm.com, mingo@elte.hu, orenl@cs.columbia.edu, linux-api@vger.kernel.org, containers@lists.linux-foundation.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, torvalds@linux-foundation.org, viro@zeniv.linux.org.uk, hpa@zytor.com, tglx@linutronix.de List-Id: linux-api@vger.kernel.org On Thu, 12 Feb 2009 13:30:35 -0600 Matt Mackall wrote: > On Thu, 2009-02-12 at 10:11 -0800, Dave Hansen wrote: > > > > - In bullet-point form, what features are missing, and should be added? > > > > * support for more architectures than i386 > > * file descriptors: > > * sockets (network, AF_UNIX, etc...) > > * devices files > > * shmfs, hugetlbfs > > * epoll > > * unlinked files > > > * Filesystem state > > * contents of files > > * mount tree for individual processes > > * flock > > * threads and sessions > > * CPU and NUMA affinity > > * sys_remap_file_pages() > > I think the real questions is: where are the dragons hiding? Some of > these are known to be hard. And some of them are critical checkpointing > typical applications. If you have plans or theories for implementing all > of the above, then great. But this list doesn't really give any sense of > whether we should be scared of what lurks behind those doors. How close has OpenVZ come to implementing all of this? I think the implementatation is fairly complete? If so, perhaps that can be used as a guide. Will the planned feature have a similar design? If not, how will it differ? To what extent can we use that implementation as a tool for understanding what this new implementation will look like? -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org