Changes
Jump to navigation
Jump to search
← Older edit
Newer edit →
Shared memory
(edit)
Revision as of 10:44, 2 September 2016
701 bytes added
,
10:44, 2 September 2016
→=
Line 56:
Line 56:
The changes tracking made developers implement [[Memory images deduplication]] for shmem segments as well.
The changes tracking made developers implement [[Memory images deduplication]] for shmem segments as well.
−
===
+
==
Dumping present pages
=
=
+
+
When dumping the contents of shared memory CRIU doesn't dump all the data. Instead, it determines which pages contain
+
it and dumps only them. This is done similarly to how regular [[memory dumping and restoring]] works, i.e. by analyzing
+
the owners' pagemap entries for PRESENT or SWAPPED bits. But there's one feature of shmem dumps -- sometimes shmem
+
page can exist in the kernel, but not mapped to any process. In this case criu detects one by calling mincore() on
+
the shmem segment, which reports back the page in-memory status. And the mincore bitmap is AND-ed with the per-process
+
ones.
+
+
== See also ==
+
+
[[Memory dumping and restoring]]
+
[[Memory images deduplication]]
[[Category:Memory]]
[[Category:Memory]]
[[Category:Under the hood]]
[[Category:Under the hood]]
Xemul
Bureaucrats
,
Administrators
2,257
edits
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Request account
Log in
Namespaces
Page
Discussion
Variants
Views
Read
Edit
View history
More
Search
Navigation
Main page
Recent changes
Random page
Help
Tools
Special pages
Printable version
News
Twitter
YouTube
External resources
Github / source code
Issues / bugs
Mr. Jenkins
Open Hub
OpenVZ