- Ajuda Scilab
- Computações Paralelas com PVM
- pvm
- pvm_addhosts
- pvm_barrier
- pvm_bcast
- pvm_bufinfo
- pvm_config
- pvm_delhosts
- pvm_error
- pvm_exit
- pvm_f772sci
- pvm_get_timer
- pvm_getinst
- pvm_gettid
- pvm_gsize
- pvm_halt
- pvm_joingroup
- pvm_kill
- pvm_lvgroup
- pvm_mytid
- pvm_parent
- pvm_probe
- pvm_recv
- pvm_reduce
- pvm_sci2f77
- pvm_send
- pvm_set_timer
- pvm_spawn
- pvm_spawn_independent
- pvm_start
- pvm_tasks
- pvm_tidtohost
- pvmd3
Please note that the recommended version of Scilab is 2025.0.0. This page might be outdated.
However, this page did not exist in the previous stable version.
pvm_barrier
blocks the calling process until all processes in a group have called it.
Calling Sequence
[info] = pvm_barrier(group,count)
Arguments
- type
string, name of an existing group.
- count
integer, specifying the number of group members that must call pvm_barrier before they are all released.
- info
integer, status code returned by the routine.
Description
pvm_barrier blocks the calling process until count
members of the group have called pvm_barrier.
The count argument is required because processes could be
joining the given group after other processes have called
pvm_barrier. Thus PVM does not know how many group members
to wait for at any given instant. Although count can be set less,
it is typically the total number of members of the group.
So the logical function of the pvm_barrier call
is to provide a group synchronization.
During any given barrier call all participating group members
must call barrier with the same count value.
Once a given barrier has been successfully passed,
pvm_barrier can be called again by the same group using the same
group name.
The returned value infowill be zero if
pvm_barrier is successful and will be
will be < 0 if some error occurs.
See Also
- pvm_joingroup — enrolls the calling process in a named group.
| << pvm_addhosts | Computações Paralelas com PVM | pvm_bcast >> |