On Tue, May 07, 2013 at 01:38:10PM +0200, Andrew Jones wrote: > What about instead of adding a new syscall (remap_anon_pages) to > instead extend mremap with new flags giving it a strict mode?
I actually thought about this and it's a very interesting argument. When I thought about it, I felt the problem was that we won't know until we did some work (at least until reaching _each_ individual page structure of every page mapped in the mremapped range) if we can avoid the vma mangling or not. So then remap_anon_pages should be more efficient because it will just error out if strict mode is not possible, it won't need to search all page structures before it know if it has to do the vma mangling or not. It likely is simpler too than to try to teach mremap to do both things after checking which one it can do. Also, the same argument could be made about remap_file_pages too. But it's still an interesting point, let's see what others thinks about it. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
