18.2.154. MPI_File_set_view
MPI_File_set_view — Changes process’s view of data in file (collective).
18.2.154.1. SYNTAX
18.2.154.1.1. C Syntax
int MPI_File_set_view(MPI_File fh, MPI_Offset disp, MPI_Datatype
etype, MPI_Datatype filetype, const char* datarep, MPI_Info
info)
18.2.154.1.2. Fortran Syntax
USE MPI
! or the older form: INCLUDE 'mpif.h'
MPI_FILE_SET_VIEW(FH, DISP, ETYPE, FILETYPE, DATAREP, INFO, IERROR)
INTEGER FH, ETYPE, FILETYPE, INFO, IERROR
INTEGER(KIND=MPI_OFFSET_KIND) DISP
CHARACTER*(*) DATAREP
18.2.154.1.3. Fortran 2008 Syntax
USE mpi_f08
MPI_File_set_view(fh, disp, etype, filetype, datarep, info, ierror)
TYPE(MPI_File), INTENT(IN) :: fh
INTEGER(KIND=MPI_OFFSET_KIND), INTENT(IN) :: disp
TYPE(MPI_Datatype), INTENT(IN) :: etype, filetype
CHARACTER(LEN=*), INTENT(IN) :: datarep
TYPE(MPI_Info), INTENT(IN) :: info
INTEGER, OPTIONAL, INTENT(OUT) :: ierror
18.2.154.2. INPUT/OUTPUT PARAMETER
fh: File handle (handle).
18.2.154.3. INPUT PARAMETERS
disp: Displacement (integer).etype: Elementary data type (handle).filetype: File type (handle). See Restrictions, below.datarep: Data representation (string).info: Info object (handle).
18.2.154.4. OUTPUT PARAMETER
ierror: Fortran only: Error status (integer).
18.2.154.5. DESCRIPTION
The MPI_File_set_view routine changes the process’s view of the data in the file — the beginning of the data accessible in the file through that view is set to disp; the type of data is set to etype; and the distribution of data to processes is set to filetype. In addition, MPI_File_set_view resets the independent file pointers and the shared file pointer to zero. MPI_File_set_view is collective across the fh; all processes in the group must pass identical values for datarep and provide an etype with an identical extent. The values for disp, filetype, and info may vary. It is erroneous to use the shared file pointer data-access routines unless identical values for disp and filetype are also given. The data types passed in etype and filetype must be committed.
The disp displacement argument specifies the position (absolute offset in bytes from the beginning of the file) where the view begins.
The MPI_File_set_view interface allows the user to pass a data-representation string to MPI I/O via the datarep argument. To obtain the default value pass the value “native”. The user can also pass information via the info argument. See the HINTS section for a list of hints that can be set.
18.2.154.6. HINTS
MPI allows applications to pass MPI_Info hints to
MPI_File_open, MPI_File_set_view, and
MPI_File_set_info. Hints are advisory: OMPIO may ignore hints
that are not supported in the selected component stack. The
MPI_File_get_info routine returns a new MPI_Info object
containing the public hints that OMPIO currently associates with the
file. The caller is responsible for freeing that returned object with
MPI_Info_free.
OMPIO preserves the spelling of a supported hint that was accepted
from the user’s MPI_Info object. When OMPIO reports an internal
default that did not come from a user-supplied hint, it uses the
canonical public spelling shown below.
18.2.154.6.1. OMPIO common hints
Hint |
Accepted by |
Default / MCA parameter |
Notes |
|---|---|---|---|
|
|
|
Size, in bytes, of the temporary collective I/O buffer on each aggregator. |
|
|
|
Number of collective I/O aggregators. When OMPIO is using its
automatic aggregator selection, this hint is not returned as
|
|
|
|
Controls whether collective buffering is enabled for collective I/O decisions. |
18.2.154.6.3. Lustre fs component hints
The Lustre layout hints affect file layout creation. Lustre applies these settings only when a file is created in a mode where layout can be set safely; changing them after a file has been opened does not change the already-created file layout.
Canonical hint |
Accepted alias |
Accepted by |
Default / MCA parameter |
Notes |
|---|---|---|---|---|
|
|
|
|
Stripe size in bytes. |
|
|
|
|
Number of Lustre object storage targets to stripe across. |
If an application supplies an alias, MPI_File_get_info returns the alias spelling. If both a canonical hint and its alias are supplied, OMPIO prefers the canonical spelling. If only an MCA parameter supplies the value, OMPIO reports the canonical spelling.
18.2.154.6.4. GPFS fs component hints
The GPFS component accepts the hints listed below when the GPFS
component is built and selected. These hints are consumed when the
file is opened. Later MPI_File_set_info or MPI_File_set_view
calls do not reapply them to GPFS, and MPI_File_get_info
continues to report the open-time accepted values.
Hint |
Accepted by |
Default / MCA parameter |
Notes |
|---|---|---|---|
|
|
No default; no corresponding MCA parameter. |
Enables optional SIOX-assisted GPFS I/O selection when SIOX support is compiled in. |
|
|
No default; no corresponding MCA parameter. |
Passed to GPFS as an access range hint. |
|
|
No default; no corresponding MCA parameter. |
Passed to GPFS as a free range hint. |
|
|
No default; no corresponding MCA parameter. |
Requests GPFS file-cache clearing. |
|
|
No default; no corresponding MCA parameter. |
Requests cancellation of GPFS hints. |
|
|
No default; no corresponding MCA parameter. |
Passed to GPFS as a replication hint. |
|
|
No default; no corresponding MCA parameter. |
Passed to GPFS as a byte range hint. |
|
|
No default; no corresponding MCA parameter. |
Requests GPFS data restriping. |
When SIOX support is compiled in, the GPFS component also accepts:
sioxAccessRange, sioxFreeRange, sioxClearFileCache,
sioxCancelHints, sioxDataShipStart, sioxDataShipStop,
sioxSetReplication, sioxByteRange, and
sioxRestripeData.
18.2.154.7. ERRORS
Almost all MPI routines return an error value; C routines as the return result of the function and Fortran routines in the last argument.
Before the error value is returned, the current MPI error handler associated with the communication object (e.g., communicator, window, file) is called. If no communication object is associated with the MPI call, then the call is considered attached to MPI_COMM_SELF and will call the associated MPI error handler. When MPI_COMM_SELF is not initialized (i.e., before MPI_Init/MPI_Init_thread, after MPI_Finalize, or when using the Sessions Model exclusively) the error raises the initial error handler. The initial error handler can be changed by calling MPI_Comm_set_errhandler on MPI_COMM_SELF when using the World model, or the mpi_initial_errhandler CLI argument to mpiexec or info key to MPI_Comm_spawn/MPI_Comm_spawn_multiple. If no other appropriate error handler has been set, then the MPI_ERRORS_RETURN error handler is called for MPI I/O functions and the MPI_ERRORS_ABORT error handler is called for all other MPI functions.
Open MPI includes three predefined error handlers that can be used:
MPI_ERRORS_ARE_FATALCauses the program to abort all connected MPI processes.MPI_ERRORS_ABORTAn error handler that can be invoked on a communicator, window, file, or session. When called on a communicator, it acts as if MPI_Abort was called on that communicator. If called on a window or file, acts as if MPI_Abort was called on a communicator containing the group of processes in the corresponding window or file. If called on a session, aborts only the local process.MPI_ERRORS_RETURNReturns an error code to the application.
MPI applications can also implement their own error handlers by calling:
Note that MPI does not guarantee that an MPI program can continue past an error.
See the MPI man page for a full list of MPI error codes.
See the Error Handling section of the MPI-4.1 standard for more information.