On 04/28/2010 10:55 PM, Minchan Kim wrote:
When you tried anon_vma_chain patches as I pointed out, what I have a concern is parent's vma not child's one. The vma of parent still has N anon_vma.
No, it is the other way around. The anon_vma of the parent is also present in all of the children, so the parent anon_vma is attached to N vmas. However, the parent vma only has 1 anon_vma attached to it, and each of the children will have 2 anon_vmas. That is what should keep any locking overhead with this patch minimal. Yes, a deep fork bomb can slow itself down. Too bad, don't do that :) -- All rights reversed -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>