Jump to: navigation, search

Memory changes tracking

1 byte removed, 00:19, 30 August 2016
How we track memory changes: kill double vertical space
* Get what pages were modified by task by reading its <code>/proc/$pid/pagemap</code> file and looking at so called ''soft-dirty'' bit in the pagemap entries.
On the first step kernel will re-map all the tasks' mapping in read-only manner. If a task will try to write into one of its pages later, a page fault would occur and the kernel would note which page was written to. Reading the <code>pagemap</code> file reveals this information.

Navigation menu