Date: Tue, 16 Feb 2016 16:17:46 GMT From: Martin Simmons <martin@lispworks.com> To: Konstantin Belousov <kostikbel@gmail.com> Cc: vangyzen@FreeBSD.org, threads@FreeBSD.org, arch@FreeBSD.org Subject: Re: libthr shared locks Message-ID: <201602161617.u1GGHkil023634@higson.cam.lispworks.com> In-Reply-To: <20160215175621.GU91220@kib.kiev.ua> (message from Konstantin Belousov on Mon, 15 Feb 2016 19:56:21 %2B0200) References: <20151223172528.GT3625@kib.kiev.ua> <56BE69B8.9020808@FreeBSD.org> <20160213143815.GB91220@kib.kiev.ua> <201602151417.u1FEHKwL003392@higson.cam.lispworks.com> <20160215144410.GT91220@kib.kiev.ua> <201602151735.u1FHZXKV006190@higson.cam.lispworks.com> <20160215175621.GU91220@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> On Mon, 15 Feb 2016 19:56:21 +0200, Konstantin Belousov said: > > One process which executed pthread_barrier_init(), performed what you > proposed. What should do the pthread_barrier_wait() call in another > process, which shares the 'barrier' with the first process, but does > not share the whole address space ? After your pthread_barrier_init() > executed, barrier contains the address of the object (off-page) in the > other address space, for that process. Ah, sorry, I understand now (the init functions are called before any sharing). How should the destroy functions be used by the processes? I.e. should only the "last" process call destroy or can every process call it?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201602161617.u1GGHkil023634>