From: Jean-Paul Dzisiak Newsgroups: comp.parallel.mpi Subject: MPI_SSEND and MPICH 1.1 Date: Fri, 12 Feb 1999 16:46:47 +0100 Organization: Environment Center - ULg Message-Id: <36C44CE6.955190C4@ulg.ac.be> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------428974CFCE629482AE056617" Xref: ukc comp.parallel.mpi:4623 --------------428974CFCE629482AE056617 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Hello ! I've tried to substitute MPI_SEND by MPI_SSEND in order to wait the completion of the MPI_RECV of the receiving process before the send command returns, but MPI_SSEND seems to work like MPI_SEND (the receiver may not have posted an MPI_RECV) and the sender takes a large amount of CPU ... What's going wrong with this statement ? Help would be very appreciated ... -- Jean-Paul Dzisiak CEME - Universit=E9 de Li=E8ge Centre d'Etude et de Mod=E9lisation de l'Environnement Sart-Tilman B5 B-4000 Li=E8ge BELGIQUE T=E9l +32 (0) 4 366 23 56 Fax +32 (0) 4 366 23 55 e-mail JP.Dzisiak@ulg.ac.be --------------428974CFCE629482AE056617 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hello !

I've tried to substitute MPI_SEND by MPI_SSEND in order to wait the completion of the MPI_RECV of the receiving process before the send command returns, but MPI_SSEND seems to work like MPI_SEND (the receiver may not have posted an MPI_RECV) and the sender takes a large amount of CPU ...

What's going wrong with this statement ?

Help would be very appreciated ... 

-- 
Jean-Paul Dzisiak

CEME - Université de Liège
Centre d'Etude et de Modélisation de l'Environnement
Sart-Tilman B5
B-4000 Liège
BELGIQUE

Tél +32 (0) 4 366 23 56
Fax +32 (0) 4 366 23 55
e-mail JP.Dzisiak@ulg.ac.be
  --------------428974CFCE629482AE056617--