Changes

Jump to navigation Jump to search
216 bytes added ,  15:12, 31 August 2016
Line 11: Line 11:  
=== On the fly ===
 
=== On the fly ===
   −
The <code>--auto-dedup</code> option can be used for <code>criu dump</code> and <code>criu page-server</code>. It causes every write to images with process' pages to punch holes in the respective parent images, which is extremely useful in [[disk-less migration]] scenario.
+
The <code>--auto-dedup</code> option can be used for <code>criu dump</code>, <code>criu pre-dump</code> and <code>criu page-server</code>. It causes every write to images with process' pages to punch holes in the respective parent images, which is extremely useful in [[disk-less migration]] scenario.
    
The <code>--auto-dedup</code> option can also be used for <code>criu restore</code>. This makes CRIU to punch holes in images as memory is being restored. This should be used if images are stored on tmpfs (i.e. in RAM, see [[disk-less migration]]), as this way RAM usage is not growing.
 
The <code>--auto-dedup</code> option can also be used for <code>criu restore</code>. This makes CRIU to punch holes in images as memory is being restored. This should be used if images are stored on tmpfs (i.e. in RAM, see [[disk-less migration]]), as this way RAM usage is not growing.
    
== Shared memory deduplication ==
 
== Shared memory deduplication ==
''Main article: [[Shared memory]]
+
''Main article: [[Shared memory]]''
An experimental shared memory deduplication is currently (August 2016) available in CRIU development branch.
+
 
 +
Deduplication only makes sense for incremental memory dumps. For now CRIU can only track changes, create incremental checkpoints and do dedup for anonymous memory. Changes tracking, increments and deduplication for shared memory is currently (August 2016) available in CRIU development branch.
    
== Implementation notes ==
 
== Implementation notes ==

Navigation menu