16
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − [[Category:GSoC]] − Line 40:
Line 38: + + + + + + + + + + + + + + + +
Add completed project (Porting CRIT to Go)
=== Restrict checks for open/mmaped files ===
=== Restrict checks for open/mmaped files ===
* [[Memory dumping and restoring]], [[Memory changes tracking]]
* [[Memory dumping and restoring]], [[Memory changes tracking]]
* [http://man7.org/linux/man-pages/man2/process_vm_readv.2.html process_vm_readv(2)] [http://man7.org/linux/man-pages/man2/vmsplice.2.html vmsplice(2)] [https://lkml.org/lkml/2018/1/9/32 RFC for splice_process_vm syscall]
* [http://man7.org/linux/man-pages/man2/process_vm_readv.2.html process_vm_readv(2)] [http://man7.org/linux/man-pages/man2/vmsplice.2.html vmsplice(2)] [https://lkml.org/lkml/2018/1/9/32 RFC for splice_process_vm syscall]
=== Porting crit functionalities in GO ===
'''Summary:''' Implement image view and manipulation in Go
'''Merged:''' https://github.com/checkpoint-restore/go-criu/pull/66
CRIU's checkpoint images are stored on disk using protobuf. For easier analysis of checkpoint files CRIU has a tool called [[CRIT|CRiu Image Tool (CRIT)]]. It can display/decode CRIU image files from binary protobuf to JSON as well as encode JSON files back to the binary format. With closer integration of CRIU in container runtimes it becomes important to be able to view the CRIU output files. Either for manipulation before restoring or for reading checkpoint statistics (memory pages written to disk, memory pages skipped, process downtime).
Currently CRIT is implemented in Python, for easier integration in other Go projects it is important to have image manipulation and analysis available from GO. This means we need a Go based library to read/modify/write/encode/decode CRIU's image files. Based on this library a Go based implementation of CRIT would be useful.
'''Links:'''
* [[CRIT (Go library)]]
* https://github.com/snprajwal/gsoc-2022
[[Category:GSoC]]