Subj : Re: Memory synchronization with pthreads
To   : comp.programming.threads
From : Joseph Seigh
Date : Mon Jan 17 2005 07:58 am

On Mon, 17 Jan 2005 09:55:15 +0100, Alexander Terekhov <terekhov@web.de> wrote:

>
> Joseph Seigh wrote:
> [...]
>> fork isn't a pthreads function.
>
> Fork is listed in the XBD 4.10. But the XBD 4.10 is busted. Obscure
> term "memory synchronization" must die.
>
> http://www.opengroup.org/austin/mailarchives/ag/msg07649.html
> http://groups.google.de/groups?selm=41C301DF.5B50EDB7%40web.de
>
> -----
> Applications shall ensure that access to any memory location by more
> than one thread is restricted such that no thread can read or modify
> a memory location while another thread of control may be modifying it.
> Applications shall use functions listed below that synchronize thread
> execution and ensure that modifications to locations in memory are
> ordered with respect to accesses to the same memory locations in other
> threads. There is a happens-before inter-thread ordering with respect
> to preceding (in program and inter-thread order) modifications of
> memory locations in
>
>   a thread calling pthreads_create() and accesses to modified memory
>   locations in the created thread;
>
>   a thread calling fork() and accesses to modified memory locations
>   in the initial thread of the created process;

I'm not sure what that means.  Is that the busted definition?

-- 
Joe Seigh

.