[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4CE6A076.2020807@kernel.org>
Date: Fri, 19 Nov 2010 17:06:14 +0100
From: Tejun Heo <tj@...nel.org>
To: Alexey Dobriyan <adobriyan@...il.com>
CC: Kirill Korotaev <dev@...allels.com>,
Serge Hallyn <serge.hallyn@...onical.com>,
Kapil Arya <kapil@....neu.edu>,
Gene Cooperman <gene@....neu.edu>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Pavel Emelianov <xemul@...allels.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Linux Containers <containers@...ts.osdl.org>
Subject: Re: [Ksummit-2010-discuss] checkpoint-restart: naked patch
Hello,
On 11/19/2010 05:00 PM, Alexey Dobriyan wrote:
> On Fri, Nov 19, 2010 at 5:33 PM, Tejun Heo <tj@...nel.org> wrote:
>>> - insert SKB's into socket buffers
>>
>> Can't we drain kernel buffers? ie. Stop further writing and wait the
>> send-q to drop to zero.
>
> On send:
> if network dies right after freeze, you lose.
Gosh, if you're really worried about that, put a netfilter module
which would buffer and simulate acks to extract the packets before
initiating freeze. These are fringe problems. Use fringe solutions.
> On receive:
> packets arrive after process freeze, but before network device freeze.
Just store the data somewhere. The checkpointer can drain the socket,
right?
>>> - setting different statistics counters (like netdev stats etc.)
>>> and so on...
>>
>> Why would this matter?
>
> Because you'll introduce million stupid interfaces not interesting to
> anyone but C/R.
In this thread, how many have you guys come up with? Not even a dozen
and most can be sovled almost trivially. Seriously, what the hell..
Thanks.
--
tejun
--
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