On Nov 29, 2010, at 6:25 PM, George Bosilca wrote: > The main problem is that openib require to pin memory pages in order to take > advantage of RMA features. There is a major issues with these pinned pages > and fork, leading to segmentation fault in some specific cases. However, we > only pin the pages on the MPI calls related to data transfers. Therefore, if > you call fork __before__ any other MPI data transfer function (but after > MPI_Init as you use the process rank), your application should be safe.
Note that Open MPI also pins some internal memory during MPI_INIT, but that memory is totally internal to libmpi, so you should be safe (i.e., you should never be able to find it and therefore never be able to try to touch it). >> How can one be sure that the disabling the warning is ok? Could you please >> elaborate on what makes forks vulnerable? May be that will guide the >> developers to make an informed decision on whether to disable them or find >> another alternative. > > No way to know at 100%. Now for an elaborate answer: Once upon a time ... The > fork story is a long and boring one, we would all have preferred to never > heard about it (believe me). A quick and compressed version can be found on > the QLogic download page > (http://filedownloads.qlogic.com/files/driver/70277/release_QLogicIB-Basic_4400_Rev_A.html). That's a good summary. The issue is with OFED itself, not with Open MPI. Note, too, that calling popen() should also be safe (even though we'll warn about it -- our atfork hook has no way of knowing whether you're calling system, popen, or something else). -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
