MPI_Address(3) LAM/MPI MPI_Address(3)NAME
MPI_Address - Gets the address of a location in memory
SYNOPSIS
#include <mpi.h>
int MPI_Address(void *loc, MPI_Aint *paddr)
INPUT PARAMETERS
loc - location in caller memory (choice)
OUTPUT PARAMETER
paddr - address of location (handle)
NOTES
This function is deprecated. It has been replaced with an MPI-2 function (see the "See also" section, below), which provides the same
functionality. This function is (or effectively is) a wrapper to the replacement function, anyway. User programs should use the MPI-2
replacement function instead of this function.
Some functions are deprecated because their names did not conform to the stricter naming conventions of MPI-2; others are deprecated
because they have been replaced with more flexible functionality.
SEE ALSO
MPI_Get_address
MORE INFORMATION
For more information, please see the official MPI Forum web site, which contains the text of both the MPI-1 and MPI-2 standards. These
documents contain detailed information about each MPI function (most of which is not duplicated in these man pages).
http://www.mpi-forum.org/
ACKNOWLEDGEMENTS
The LAM Team would like the thank the MPICH Team for the handy program to generate man pages ("doctext" from ftp://ftp.mcs.anl.gov/pub/sow-
ing/sowing.tar.gz ), the initial formatting, and some initial text for most of the MPI-1 man pages.
LOCATION
address.c
LAM /MPI 6.5.8 11/10/2002 MPI_Address(3)
Check Out this Related Man Page
MPI_Type_extent(3) LAM/MPI MPI_Type_extent(3)NAME
MPI_Type_extent - Returns the extent of a datatype
SYNOPSIS
#include <mpi.h>
int MPI_Type_extent(MPI_Datatype dtype, MPI_Aint *pextent)
INPUT PARAMETERS
dtype - datatype (handle)
OUTPUT PARAMETER
pextent
- datatype extent (integer)
NOTES
This function is deprecated. It has been replaced with an MPI-2 function (see the "See also" section, below), which provides the same
functionality. This function is (or effectively is) a wrapper to the replacement function, anyway. User programs should use the MPI-2
replacement function instead of this function.
Some functions are deprecated because their names did not conform to the stricter naming conventions of MPI-2; others are deprecated
because they have been replaced with more flexible functionality.
SEE ALSO
MPI_Type_get_extent
MORE INFORMATION
For more information, please see the official MPI Forum web site, which contains the text of both the MPI-1 and MPI-2 standards. These
documents contain detailed information about each MPI function (most of which is not duplicated in these man pages).
http://www.mpi-forum.org/
ACKNOWLEDGEMENTS
The LAM Team would like the thank the MPICH Team for the handy program to generate man pages ("doctext" from ftp://ftp.mcs.anl.gov/pub/sow-
ing/sowing.tar.gz ), the initial formatting, and some initial text for most of the MPI-1 man pages.
LOCATION
textent.c
LAM /MPI 6.5.8 11/10/2002 MPI_Type_extent(3)
So I have been struggling for the past few days to install a simulation package lammps (http://lammps.sandia.gov/) on my Mac OS X. I am well aware that this is a Ubuntu forum, but you guys seem to know a lot of UNIX stuff, so I was hoping someone might have a solution to my problem...
To run... (1 Reply)
In setting up an 8e on 5.0.5 I couldn't find a memory window that worked using mpi (3 versions).
The memory search program (DOS based) indicated E800 was available but mpi only listed E000.
I resolved my immediate problem by changing the window value in /etc/conf/pack.d/pcxx/space.c prior to... (2 Replies)
I'm trying to run MPI programs on 8 machines, but I get the error
connect to address 127.0.0.1 port 544: Connection refused
Trying krb4 rsh...
connect to address 127.0.0.1 port 544: Connection refused
trying normal rsh (/usr/bin/rsh)
lagrid02: Connection refused
When I run it with a... (8 Replies)
Discussion started by: vishwamitra
8 Replies
5. Post Here to Contact Site Administrators and Moderators
Hello Admin/moderators Team,
Greetings !!
This is regarding a suggestion which may help our forum if this is possible.
Thanks,
R. Singh
"GOD helps those who help themselves" (2 Replies)