[Omp] flush x other synchronization operations

[Patricia Bittencourt Sampaio]

 Hello,

    I am a little confused about the difference
between flush and other synchronization constructs.

    As OpenMP uses a Relaxed Consistency Memory Model,
a barrier just like the end of a critical section or
every operation that involves a page release, imposes
a point of a consistent view of memory. In a way that
subsequenttelly reads of a location that is shared
among the threads will require the access to memory
and not to the local instance of each thread.

    According to the behave of the flush operation,
that is exactly what it does.

    So, I presume that the differences between flush
and other synchronization operations are just twice:

- Flush enforces a consistent view of memory with
respect to a flush set (when it is specified) and not
related to all shared variables as a barrier
synchronization does.

- In the case of a barrier, it requires that each
thread of a team wait for all other threads to arrive
at the barrier, while flush does not imposes this
roll.

    Am I wrong about this? Do you recognize other
differences?

Best regards,


Patricia B. Sampaio
====================================
Federal University of Rio de Janeiro
      


		
_______________________________________________________ 
Novidade no Yahoo! Mail: receba alertas de novas mensagens no seu celular. Registre seu aparelho agora! 
http://br.mobile.yahoo.com/mailalertas/