Changes

Jump to navigation Jump to search

Comparison to other CR projects (edit)

Revision as of 19:20, 9 December 2015

1,599 bytes added ,  19:20, 9 December 2015
added absent architectures for criu
Line 1: Line 1:  
This pages tries to explain differences between CRIU and other C/R solutions.
 
This pages tries to explain differences between CRIU and other C/R solutions.
   −
== [http://dmtcp.sourceforge.net DMTCP] ==
+
== DMTCP ==
    
{{:DMTCP}}
 
{{:DMTCP}}
   −
== [https://ftg.lbl.gov/projects/CheckpointRestart BLCR] ==
+
== BLCR ==
    
Berkeley Lab Checkpoint/Restart (BLCR) is a part of the Scalable Systems Software Suite ,  
 
Berkeley Lab Checkpoint/Restart (BLCR) is a part of the Scalable Systems Software Suite ,  
Line 15: Line 15:  
small LGPL-licensed library.
 
small LGPL-licensed library.
   −
== [http://criu.org CRIU], [http://dmtcp.sourceforge.net DMTCP], [https://ftg.lbl.gov/projects/CheckpointRestart BLCR] ==
+
== PinLIT / PinPlay ==
 +
 
 +
PinLIT (Pin-Long Instruction Trace) is a checkpointing tool built on top of Intel's proprietary [https://software.intel.com/en-us/articles/pin-a-dynamic-binary-instrumentation-tool PIN binary instrumentation tool] described on page 48 of [https://cseweb.ucsd.edu/~calder/papers/thesis-cristiano.pdf Cristiano Pereira's PhD thesis]. It records the processor's (big) architectural register state and all pages of memory that contain application and shared library code, optimizing size by only storing memory used during a desired interval.
 +
 
 +
[https://software.intel.com/en-us/articles/program-recordreplay-toolkit PinPlay] or the Program Record/Replay Toolkit appears to be the successor of or new name for PinLIT.
 +
 
 +
Both tools appear primarily focused on reducing benchmark runtime on slow computer architecture simulators, leveraging sampling algorithms such as SimPoint.
 +
 
 +
== OpenVZ (in-kernel) ==
 +
 
 +
Legacy OpenVZ (RHEL4, RHEL5, RHEL6 based kernels) has in-kernel checkpoint/restore, sources can be found in kernel/cpt/.
 +
 
 +
== CKPT (in-kernel) ==
 +
 
 +
(In-kernel) [https://ckpt.wiki.kernel.org/index.php/Main_Page Linux Checkpoint/Restart] was a project from around 2008 to around 2010 to implement checkpoint/restart of Linux processes.
 +
 
 +
== CRIU, DMTCP, BLCR, OpenVZ comparison table ==
 
   
 
   
 
“looks\seems like yes/no” - i found only unproved message(s) saying “yes”/“no”
 
“looks\seems like yes/no” - i found only unproved message(s) saying “yes”/“no”
Line 32: Line 48:  
|-
 
|-
 
| Arch
 
| Arch
−
| x86_64, ARM
+
| x86_64, ARM, AArch64, PPC64le
 
| x86, x86_64, ARM
 
| x86, x86_64, ARM
 
| x86, x86_64, PPC/PPC64, ARM
 
| x86, x86_64, PPC/PPC64, ARM
Line 45: Line 61:     
|-
 
|-
−
| Need in modified kernel
+
| Uses standard kernel?
−
| Yes, but only for some extra features. All unnecessary features are already in new kernel versions
+
| {{Yes}}, provided it's 3.11 or later
−
| No
+
| {{Yes}}
−
| No, just need to load module. May be problems with installation on new kernels
+
| {{Yes}}, just needs to load module
−
| Yes
+
| {{No}}. OpenVZ kernel is required
    
|-
 
|-
−
| App need to pre-load special libraries
+
| Can be used without preloading special libraries before app start?
−
| No
+
| {{Yes}}
−
| Yes
+
| {{No}}
−
| Yes
+
| {{No}}
−
| No
+
| {{Yes}}
    
|-
 
|-
−
| Requires root privileges
+
| Can be used as non-root user?
−
| Yes, due to restrictions from some kernel APIs it uses
+
| {{Yes}}, but user can only manipulate tasks belonging to him
−
| No
+
| {{Yes}}
−
| No
+
| {{Yes}}
−
| Yes
+
| {{No}}
    
|-
 
|-
−
| Need to modify programs to C/R
+
| Can run unmodified programs?
−
| No
+
| {{Yes}}
−
| No
+
| {{Yes}}
−
| Yes. There are some difficulties with statically linked applications, and with LinuxThreads (it does not support them at all)
+
| {{No}}. Statically linked and/or threaded apps are unsupported.
−
| No
+
| {{Yes}}
−
 
      
|-
 
|-
−
| Need to prepare tasks
+
| Can run unprepared tasks?
−
| No
+
| {{Yes}}
−
| Yes. It preloadsthe DMTCP library. That library runs before the routinemain(). It creates a second thread. Thecheckpoint thread then creates a socket to the DMTCP coordinator andregisters itself. The checkpoint thread also creates a signal handler.
+
| {{No}}. It preloads the DMTCP library. That library runs before the routine main(). It creates a second thread. The checkpoint thread then creates a socket to the DMTCP coordinator and registers itself. The checkpoint thread also creates a signal handler.
−
| Yes. CR shall notify processes when a checkpoint is to occur (before the kernel takes a checkpoint) to allow the processes to prepare itself accordingly.
+
| {{No}}. CR shall notify processes when a checkpoint is to occur (before the kernel takes a checkpoint) to allow the processes to prepare itself accordingly.
−
| No
+
| {{Yes}}
−
 
      
|-
 
|-
−
| Does it change behavior of the c/r-ed programs?
+
| Retains behavior of the c/r-ed programs?
−
| No
+
| {{Yes}} (but see [[What can change after C/R]])
−
| Yes, because of wrappers on system calls
+
| {{No}}, because of wrappers on system calls
−
| Yes, because of wrappers on system calls
+
| {{No}}, because of wrappers on system calls
−
| No
+
| {{Yes}}
    
|-
 
|-
 
| Live migration
 
| Live migration
−
| Yes, even if kernel, libs, etc are newer. Can use Memory Changes Tracking to decrease freeze time
+
| {{Yes}}, even if kernel, libs, etc are newer. Can use [[memory changes tracking]] to decrease freeze time
−
| Yes, if both kernels are recent
+
| {{Yes}}, if both kernels are recent
−
| Yes, but if all components are the same. Even if prelinked addresses are different,it will not restore, but it can save the whole used libs and localization files to restore program on the different machine
+
| {{Yes}}, but if all components are the same. Even if prelinked addresses are different, it will not restore, but it can save the whole used libs and localization files to restore program on the different machine
−
| Yes
+
| {{Yes}}
    
|-
 
|-
 
| Containers
 
| Containers
−
| Yes, LXC and OpenVZ containers
+
| {{Yes}}, LXC and OpenVZ containers
−
| No. It doesn't support namespaces, so it probably can’t dump containers  
+
| {{No}}. It doesn't support namespaces, so it probably can’t dump containers  
−
| Looks like no
+
| {{No|Looks like no}}
−
| Yes
+
| {{Yes}}
    
|-
 
|-
 
| Parallel/distributed computations libraries
 
| Parallel/distributed computations libraries
−
| No (in plans)
+
| {{No}} (planned)
−
| Yes. OpenMPI, MPICH2, OpenMP, Cilk are alredy supported and Infiniband is in progress
+
| {{Yes}}. OpenMPI, MPICH2, OpenMP, Cilk are alredy supported and Infiniband is in progress
−
| Yes. Cray MPI, Intel MPI, LAM/MPI, MPICH-V, MPICH2, MVAPICH, Open MPI, SGI MPT
+
| {{Yes}}. Cray MPI, Intel MPI, LAM/MPI, MPICH-V, MPICH2, MVAPICH, Open MPI, SGI MPT
−
| Yes
+
| {{Yes}}
    
|-
 
|-
−
| C/R gdb with debugging app
+
| Possible to C/R of gdb with debugged app?
−
| No, because they are using the same interface
+
| {{No}}, because they are using the same interface
−
| Yes
+
| {{Yes}}
−
| No
+
| {{No}}
−
| Yes
+
| {{Yes}}
    
|-
 
|-
−
| X-Windows apps (KDE, GNOME, etc)
+
| X Window apps (KDE, GNOME, etc)
−
| Yes, by using vnc
+
| {{Yes}}, via VNC
−
| Yes, by using vnc
+
| {{Yes}}, via VNC
−
| Looks like no
+
| {{No|Looks like no}}
−
| Yes, by using vnc
+
| {{Yes}}, via VNC
       
|-
 
|-
 
| Solutions for invocation in the custom software
 
| Solutions for invocation in the custom software
−
| No, only fork + daemonize + exec
+
| {{Yes}}, [[RPC]] and [[C API]]
−
| Yes. Plugins and API
+
| {{Yes}}, plugins and API
−
| Not yet
+
| {{No|Not yet}}
−
| Yes. via ioctl calls
+
| {{Yes}}, via ioctl calls
    
|-
 
|-
Line 136: Line 150:  
|-
 
|-
 
| Unix sockets
 
| Unix sockets
−
| Yes
+
| {{Yes}}
−
| Yes
+
| {{Yes}}
−
| No
+
| {{No}}
−
| Yes
+
| {{Yes}}
    
|-
 
|-
 
| UDP sockets
 
| UDP sockets
−
| Yes, both ipv4 and ipv6
+
| {{Yes}}, both ipv4 and ipv6
−
| Not yet. Developers of dmtcp had no request for this
+
| {{No|Not yet}}. Developers of dmtcp had no request for this
−
| Not yet
+
| {{No|Not yet}}
−
| Yes
+
| {{Yes}}
    
|-
 
|-
 
| TCP sockets
 
| TCP sockets
−
| Yes
+
| {{Yes}}
−
| Yes
+
| {{Yes}}
−
| Not yet
+
| {{No|Not yet}}
−
| Yes
+
| {{Yes}}
    
|-
 
|-
−
| Established tcp connection
+
| Established TCP connection
−
| Yes
+
| {{Yes}}
−
| No, but you can write a simple DMTCP plugin that tells DMTCP how you want to reconnect on restart
+
| {{No}}, but you can write a simple DMTCP plugin that tells DMTCP how you want to reconnect on restart
−
| No
+
| {{No}}
−
| Yes
+
| {{Yes}}
    
|-
 
|-
 
| Infiniband
 
| Infiniband
−
| No
+
| {{No}}
−
| Not yet, developing is on the half-way
+
| {{No|Not yet, developing is on the half-way}}
−
| No
+
| {{No}}
−
| No
+
| {{No}}
    
|-
 
|-
 
| Multithread support
 
| Multithread support
−
| Yes
+
| {{Yes}}
−
| Yes
+
| {{Yes}}
−
| Yes
+
| {{Yes}}
−
| Yes
+
| {{Yes}}
    
|-
 
|-
 
| Multiprocess
 
| Multiprocess
−
| Yes
+
| {{Yes}}
−
| Yes
+
| {{Yes}}
−
| Yes
+
| {{Yes}}
−
| Yes
+
| {{Yes}}
    
|-
 
|-
 
| Process groups and sessions
 
| Process groups and sessions
−
| Yes
+
| {{Yes}}
−
| Yes
+
| {{Yes}}
−
| Not yet
+
| {{No|Not yet}}
−
| Yes
+
| {{Yes}}
    
|-
 
|-
 
| Zombies
 
| Zombies
−
| Yes
+
| {{Yes}}
−
| No
+
| {{No}}
−
| No
+
| {{No}}
−
| Yes
+
| {{Yes}}
    
|-
 
|-
 
| Namespaces
 
| Namespaces
−
| Yes
+
| {{Yes}}
−
| No
+
| {{No}}
−
| No
+
| {{No}}
−
| Yes
+
| {{Yes}}
    
|-
 
|-
 
| Ptraced programs
 
| Ptraced programs
−
| No
+
| {{No}}
−
| Yes
+
| {{Yes}}
−
| No
+
| {{No}}
−
| Yes
+
| {{Yes}}
    
|-
 
|-
 
| System V IPC
 
| System V IPC
−
| Yes
+
| {{Yes}}
−
| Yes
+
| {{Yes}}
−
| No
+
| {{No}}
−
| Yes
+
| {{Yes}}
    
|-
 
|-
 
| Memory mappings
 
| Memory mappings
−
| Yes, all kinds
+
| {{Yes}}, all kinds
−
| Yes
+
| {{Yes}}
−
| Yes, partially
+
| {{Partial}}
−
| Yes
+
| {{Yes}}
    
|-
 
|-
 
| Pipes
 
| Pipes
−
| Yes
+
| {{Yes}}
−
| Yes
+
| {{Yes}}
−
| Not yet
+
| {{No|Not yet}}
−
| Yes
+
| {{Yes}}
    
|-
 
|-
 
| Terminals
 
| Terminals
−
| Yes, but only Unix98 PTYs
+
| {{Yes}}, but only Unix98 PTYs
−
| Yes
+
| {{Yes}}
−
| Yes
+
| {{Yes}}
−
| Yes
+
| {{Yes}}
    
|-
 
|-
−
| Non-posix files (inotify, signalfd, eventfd, etc)
+
| Non-POSIX files (inotify, signalfd, eventfd, etc)
−
| Yes, inotify, fanotify, epoll, signalfd, eventfd
+
| {{Yes}}, inotify, fanotify, epoll, signalfd, eventfd
−
| Yes, epoll, eventfd, signalfd are already supported and inotify will be supported in future
+
| {{Yes}}, epoll, eventfd, signalfd are already supported and inotify will be supported in future
−
| Looks like no
+
| {{No|Looks like no}}
−
| Yes
+
| {{Yes}}
    
|-
 
|-
 
| Timers
 
| Timers
−
| Yes
+
| {{Yes}}
−
| No. Any counter or timer active since the beginning of a process will consider the restarted process to be a new process.
+
| {{No}}. Any counter or timer active since the beginning of a process will consider the restarted process to be a new process.
−
| Yes
+
| {{Yes}}
−
| Yes
+
| {{Yes}}
    
|-
 
|-
 
| Shared resources (files, mm, etc.)
 
| Shared resources (files, mm, etc.)
−
| Yes. SysVIPC, files, fd table and memory
+
| {{Yes}}. SysVIPC, files, fd table and memory
−
| Yes. System V shared memory(shmget, etc.), mmap-based shared memory, shared sockets, pipes, file descriptors
+
| {{Yes}}. System V shared memory(shmget, etc.), mmap-based shared memory, shared sockets, pipes, file descriptors
−
| No, but it is planned to suppord shared mmap regions
+
| {{No}}, but it is planned to support shared mmap regions
−
| Yes
+
| {{Yes}}
    
|-
 
|-
 
| Block devices
 
| Block devices
−
| No
+
| {{No}}
−
| Looks like yes
+
| {{Yes|Looks like yes}}
−
| No
+
| {{No}}
−
| No
+
| {{No}}
       
|-
 
|-
 
| Character devices
 
| Character devices
−
| Yes, only /dev/null, /dev/zero, etc. are supported
+
| {{Yes}}, only /dev/null, /dev/zero, etc. are supported
−
| Yes, looks like null and zero are supported
+
| {{Yes}}, looks like null and zero are supported
−
| Yes, /dev/null and /dev/zero
+
| {{Yes}}, /dev/null and /dev/zero
−
| Yes
+
| {{Yes}}
    
|-
 
|-
 
| Capture the contents of open files
 
| Capture the contents of open files
−
| Yes, if file is unlinked
+
| {{Yes}}, if file is unlinked
−
| Looks like no
+
| {{No|Looks like no}}
−
| Not yet
+
| {{No|Not yet}}
−
| Yes
+
| {{Yes}}
    
|}
 
|}
Retrieved from "https://criu.org/Special:MobileDiff/1125...2693"

Navigation menu