> So.. What is the problem with fork? The semantics of what should > happen seem natural enough to me, the PD doesn't get copied to the > child, so the MR stays with the parent. COW events on the pinned > region must be resolved so that the physical page stays with the > process that has pinned it - the pin is logically released in the > child because the MR doesn't exist because the PD doesn't exist.
This is getting away from the problem that ummunotify is solving, but handling a COW fault generated by the parent by doing the copy in the child seems like a pretty major, tricky change to make. The child may have forked 100 more times in the meantime, meaning we now have to change 101 memory maps ... the cost of page faults goes through the roof probably... - R. _______________________________________________ general mailing list general@lists.openfabrics.org http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
