One possible improvement that comes to mind would be a private vforkx() flag to request that threads in the parent other than the one calling vforkx() not be stopped. The child would have to be extremely careful to not call malloc() or do anything that might disturb the state of the parent beyond the current stack frame, which is why such a flag would have to be private and undocumented. But this should not be considered until someone first shows that posix_spawn() performance is a problem and that the parent thread stop/resume overhead is the biggest ticket item.
Nico -- _______________________________________________ on-discuss mailing list on-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/on-discuss
