Date: Tue, 27 May 2003 09:23:10 +0200 From: Morten Rodal <morten@rodal.no> To: Anthony Schneider <anthony@x-anthony.com> Cc: freebsd-current@freebsd.org Subject: Re: mpi + shmem issues Message-ID: <20030527072310.GB3290@atlantis.rodal.no> In-Reply-To: <20030525211730.GA5226@x-anthony.com> References: <20030525064929.GA96588@x-anthony.com> <20030525211730.GA5226@x-anthony.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--envbJBWh7q8WU6mo
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sun, May 25, 2003 at 05:17:30PM -0400, Anthony Schneider wrote:
> additional information:
>=20
> when recompiling mpich for debugging symbols, configure fails on:
> checking that usable shared memory locks were found... no
>=20
> so, does this mean that mpich somehow exhausted all shmem locks?
> after running the program only 10 times, i see this as infeasible,
> considering
> a) mpich (presumably in MPI_Init()) would only want 1 or
> 2 locks on init
> and
> b) any shared memory locks mpich grabs should be freed
> upon process completion (whether clean or not) by the
> operating system, no?
>=20
ALWAYS remember to call MPI_Finalize(), since it clears up stuff like
semaphores and memory allocations.
> > #include <mpi.h>
> > #include <stdio.h>
> >=20
> > int main (int argc, char *argv[]) {
> > int mpiRank, mpiSize;
> >=20
> > MPI_Init (&argc, &argv);
> > MPI_Comm_rank (MPI_COMM_WORLD, &mpiRank);
> >=20
> > printf ("#%d here\n", mpiRank);
> >=20
MPI_Finalize();
> > return 0;
> >=20
> > }
> >=20
>=20
--=20
Morten Rodal
--envbJBWh7q8WU6mo
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)
iD8DBQE+0xJebWe1Cy11WVsRAh/5AJ99JyBvNpmALaWADaUyNffx13zxOQCfQS66
fDP+7h1PDFoopMWJ4zcKFng=
=yW8R
-----END PGP SIGNATURE-----
--envbJBWh7q8WU6mo--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030527072310.GB3290>