Sophie: mpich2-doc-1.0.8-2mdv2010.0 i586

mpich2-doc-1.0.8-2mdv2010.0.i586.rpm

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML3.2 EN">
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="DOCTEXT">
<TITLE>MPE_Seq_begin</TITLE>
</HEAD>
<BODY BGCOLOR="FFFFFF">
<A NAME="MPE_Seq_begin"><H1>MPE_Seq_begin</H1></A>
Begins a sequential section of code.   
<H2>Synopsis</H2>
<PRE>
void MPE_Seq_begin( MPI_Comm comm, int ng )
</PRE>
<H2>Input Parameters</H2>
<DL>
<DT><B>comm </B><DD>Communicator to sequentialize.  

<DT><B>ng   </B><DD>Number in group.  This many processes are allowed to execute
at the same time.  Usually one.  
</DL>
<P>
<H2>Notes</H2>
'MPE_Seq_begin' and 'MPE_Seq_end' provide a way to force a section of code
to
be executed by the processes in rank order.  Typically, this is done
with
<PRE>
  MPE_Seq_begin( comm, 1 );
  &lt;code to be executed sequentially&gt;
  MPE_Seq_end( comm, 1 );
</PRE>

Often, the sequential code contains output statements (e.g., 'printf') to
be executed.  Note that you may need to flush the I/O buffers before
calling 'MPE_Seq_end'; also note that some systems do not propagate I/O in
any
order to the controling terminal (in other words, even if you flush the
output, you may not get the data in the order that you want).
<P><B>Location:</B>../src/misc/src/mpe_seq.c<P>
</BODY></HTML>