Date: Wed, 15 Aug 2012 20:46:09 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: davidxu@freebsd.org Cc: freebsd-hackers@freebsd.org, Jilles Tjoelker <jilles@stack.nl> Subject: Re: system() using vfork() or posix_spawn() and libthr Message-ID: <20120815174609.GM5883@deviant.kiev.zoral.com.ua> In-Reply-To: <502A6B7A.6070504@gmail.com> References: <20120730102408.GA19983@stack.nl> <20120730105303.GU2676@deviant.kiev.zoral.com.ua> <20120805215432.GA28704@stack.nl> <20120806082535.GI2676@deviant.kiev.zoral.com.ua> <20120809105648.GA79814@stack.nl> <5029D727.2090105@freebsd.org> <20120814081830.GA5883@deviant.kiev.zoral.com.ua> <502A1788.9090702@freebsd.org> <20120814094111.GB5883@deviant.kiev.zoral.com.ua> <502A6B7A.6070504@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--kunpHVz1op/+13PW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Aug 14, 2012 at 11:15:06PM +0800, David Xu wrote: > You are requiring the thread library to implement such a mutex > and other locks, that after vfork(), the mutex and other lock types must > still work across processes, the PTHREAD_PROCESS_PRIVATE type of > mutex and other locks now need to work in a PTHREAD_PROCESS_SHARE > mode. In fact, yes. In my patch I achieve this by single-threading the parent, which means that existing _PRIVATE mutexes are enough. --kunpHVz1op/+13PW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAlAr4GAACgkQC3+MBN1Mb4jQYwCcCuTNRr3jfB0bPouzvpWU8MC8 lF8AoMKuyTX8zUBZW3c6ty6fW1KaxwHA =yypn -----END PGP SIGNATURE----- --kunpHVz1op/+13PW--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120815174609.GM5883>