On Thu, Apr 11, 2013 at 03:29:41PM +0400, Pavel Emelyanov wrote: > This file is the same as the pagemap one, but shows entries with bits > 55-60 being zero (reserved for future use). Next patch will occupy one > of them. This approach doesn't scale as well as it could. As best I can see CRIU would do: for each vma in /proc/<pid>/smaps for each page in /proc/<pid>/pagemap2 if soft dirty bit copy page (possibly with pfn checks to avoid copying the same page mapped in multiple locations..) However, if soft dirty bit changes could be queued up (from say the fault handler and page table ops that map/unmap pages) and accumulated in something like an interval tree it could be something like: for each range of changed pages for each page in range copy page IOW something that scales with the number of changed pages rather than the number of mapped pages. So I wonder if CRIU would abandon pagemap2 in the future for something like this. Cheers, -Matt Helsley -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>