[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openvz-devel
Subject:    [Devel] Re: [RFC][PATCH 0/2] pipe: checkpoint and restart for pipe; brief description and test inter
From:       dlezcano () fr ! ibm ! com (Daniel Lezcano)
Date:       2007-01-31 9:50:29
Message-ID: 45C06665.4040605 () fr ! ibm ! com
[Download RAW message or body]

Eric W. Biederman wrote:
> Masahiko Takahashi <masahiko at linux-foundation.org> writes:
> 
>> Hi everyone,
>>
>> I would like to post a small patch that implements pipe checkpoint
>> and restart functionality.
>>
>> The patch supports pipe buffers used with splice/vmsplice systemcall.
>> Usually, spliced buffers' pages are in memory cache because their data
>> are read from an filesystem. However the patch doesn't treat buffers'
>> pages as cached memory when restoring. If trying to treat as cached
>> memory, each buffer's page should be tagged with its filename when
>> checkpointing. This is not a difficult implementation, but I'm still
>> wondering this is worth implementing...
> 
> Rewind a little bit please.  I can clearly see where checkpoint/restart
> fit into the containers conversation.
> 
> However I don't see where this checkpoint/restart patchset fits into
> the checkpoint restart picture.

it is a RFC ...

> 
> What ideas are you trying to discuss?
> 
> I will say that I am not yet convinced that we need the kernel saving
> and restoring the checkpoint.

I don't get it, do you mean checkpoint/restart should be done in 
userspace ? or simply checkpoint/restart is useless ?

_______________________________________________
Containers mailing list
Containers at lists.osdl.org
https://lists.osdl.org/mailman/listinfo/containers



[prev in list] [next in list] [prev in thread] [next in thread]