Difference between revisions of "Image field merging"

From CRIU
Jump to: navigation, search
(Created page with "The number of image files has a penalty over migration process speed. Thus we initiated the _merging_ procedure which is aimed to reduce the number of image files by merging f...")
 
Line 1: Line 1:
The number of image files has a penalty over migration process speed. Thus we initiated the _merging_ procedure which is aimed to reduce the number of image files by merging files one into another. Unfortunately we can't just merge everything into one big file because data can be shared between tasks thus only small set of files can be merged. Here is a list of merged data so far:
+
The number of image files has a penalty over migration process speed. Thus we initiated the _merging_ procedure which is aimed to reduce the number of image files by merging files one into another. Unfortunately we can't just merge everything into one big file because data can be shared between tasks thus only small set of files can be merged.
  
 +
Note because of backward compatibility requirement we need to support both merged and separate images for a while.
 +
 +
Here is a list of merged data so far:
 +
 +
* vma_entry -> mm_entry::vmas
 +
* rlimit_entry -> core_entry::task_rlimits
  
 
[[Category:Development]]
 
[[Category:Development]]

Revision as of 06:25, 14 March 2014

The number of image files has a penalty over migration process speed. Thus we initiated the _merging_ procedure which is aimed to reduce the number of image files by merging files one into another. Unfortunately we can't just merge everything into one big file because data can be shared between tasks thus only small set of files can be merged.

Note because of backward compatibility requirement we need to support both merged and separate images for a while.

Here is a list of merged data so far:

  • vma_entry -> mm_entry::vmas
  • rlimit_entry -> core_entry::task_rlimits