lkml.org 
[lkml]   [2009]   [Sep]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [PATCH 00/80] Kernel based checkpoint/restart [v18]
    From
    Date
    DL> Yep, I agree. But you didn't answer the question, what are the
    DL> network resources you plan to checkpoint / restart ? eg. you let
    DL> the container to setup your network, will you restore netdev
    DL> statistics ? the mac address ? ipv4 ? ipv6 ?

    Yes, Yes, Yes, and Yes. I'm making the assumption that the common
    case will be with a veth device in the container and that all of the
    aforementioned attributes should be copied over. In the future case
    where we could potentially have a real device in the container, it
    probably doesn't make sense to copy the mac address.

    DL> Is it possible to do a detailed list of network resources you plan
    DL> to CR with the different items you will address from userspace and
    DL> kernel space ?

    I'm sure it's possible, but no, I haven't planned out everything for
    the next year. If you have strong feelings about what should be done
    in user and kernel space, feel free to share :)

    DL> Argh ! I was hoping there was something else than the source code

    The header file makes it pretty clear what is going on, but maybe the
    Documentation/checkpoint/readme.txt will help. Putting all the
    details in such a documentation file would be rather silly at the
    moment, given that new things are being added at a rapid rate and it
    would duplicate the only description that matters, which is the
    header file.

    --
    Dan Smith
    IBM Linux Technology Center
    email: danms@us.ibm.com


    \
     
     \ /
      Last update: 2009-09-30 20:31    [W:3.551 / U:0.068 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site