On Fri, 13 Sep 2013 23:14:22 +0200 =?KOI8-R?B?z8zYx8Egy9LZ1sHOz9fTy8HR?= wrote: > Glenn, shared mmap() mapping do not have any impact on fork() > performance, at least on VM architectures who can share pages (this is > common practice since at least SystemV, and no modern Unix or Linux > exists which does not do copy-on-write, but more on that below) The > pages are not even touched, or looked at at fork() time, so even > millions of mmap() pages have no impact. > Only if the pages are touched the VM system will realize a fork() has > happened, and *may* create a copy-on-write copy if you write to it. If > you only read the pages nothing will happen.
thanks we weren't concerned about the pages themselves but the TLB or whatever the vm system uses to keep track of pages that has to be duped on fork(), no? or are you saying even that is copy on write? _______________________________________________ ast-users mailing list [email protected] http://lists.research.att.com/mailman/listinfo/ast-users
