Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758179Ab0KQPdQ (ORCPT ); Wed, 17 Nov 2010 10:33:16 -0500 Received: from gw0.danplanet.com ([71.245.107.82]:34087 "EHLO mail.danplanet.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753432Ab0KQPdP (ORCPT ); Wed, 17 Nov 2010 10:33:15 -0500 To: Tejun Heo Cc: Gene Cooperman , Oren Laadan , Kapil Arya , ksummit-2010-discuss@lists.linux-foundation.org, linux-kernel@vger.kernel.org, hch@lst.de Subject: Re: [Ksummit-2010-discuss] checkpoint-restart: naked patch References: <4CD26948.7050009@kernel.org> <20101104164401.GC10656@sundance.ccs.neu.edu> <4CD3CE29.2010105@kernel.org> <4CD5DCE3.3000109@cs.columbia.edu> <20101107194222.GG31077@sundance.ccs.neu.edu> <4CD71A6B.3020905@cs.columbia.edu> <20101107230516.GJ31077@sundance.ccs.neu.edu> <4CD774CA.8030004@cs.columbia.edu> <20101108162630.GN31077@sundance.ccs.neu.edu> <8739rbpreb.fsf@localhost6.localdomain6> <4CE3B927.1020401@kernel.org> From: Dan Smith Date: Wed, 17 Nov 2010 07:33:12 -0800 Message-ID: <8762vwvubr.fsf@localhost6.localdomain6> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1369 Lines: 35 TH> If it ever becomes a general enough problem (which I extremely TH> strongly doubt), Migration of a container? Yeah, it's one of the primary reasons for doing what we're doing :) TH> we can think about allowing processes in a netns to change TH> sequence number but that would be a single setsockopt option Yeah, well there's more than that, of course, if you want to be able to checkpoint a socket in any state. Buffers, time-wait, etc. TH> instead of the horror show of dumping in-kernel data structures in TH> binary blob. Well, as should be evident from a review of the code, we don't dump binary kernel data structures as a general rule. We canonicalize them into checkpoint headers on the way out and build the new data structures (or use existing kernel interfaces to do so) on the way in. You know, just like netlink does. It has even been suggested that we do this with netlink instead, to mirror the other "horror show" tools that we all use on a daily basis. We're not opposed to this, but we do have some concerns about performance. -- Dan Smith IBM Linux Technology Center email: danms@us.ibm.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/