Chris@82: Chris@82: Chris@82: Chris@82: Chris@82: Chris@82: FFTW 3.3.8: MPI Initialization Chris@82: Chris@82: Chris@82: Chris@82: Chris@82: Chris@82: Chris@82: Chris@82: Chris@82: Chris@82: Chris@82: Chris@82: Chris@82: Chris@82: Chris@82: Chris@82: Chris@82: Chris@82: Chris@82: Chris@82: Chris@82:
Chris@82:

Chris@82: Next: , Previous: , Up: FFTW MPI Reference   [Contents][Index]

Chris@82:
Chris@82:
Chris@82: Chris@82:

6.12.2 MPI Initialization

Chris@82: Chris@82:

Before calling any other FFTW MPI (‘fftw_mpi_’) function, and Chris@82: before importing any wisdom for MPI problems, you must call: Chris@82:

Chris@82: Chris@82:
Chris@82:
void fftw_mpi_init(void);
Chris@82: 
Chris@82: Chris@82: Chris@82:

If FFTW threads support is used, however, fftw_mpi_init should Chris@82: be called after fftw_init_threads (see Combining MPI and Threads). Calling fftw_mpi_init additional times (before Chris@82: fftw_mpi_cleanup) has no effect. Chris@82:

Chris@82: Chris@82:

If you want to deallocate all persistent data and reset FFTW to the Chris@82: pristine state it was in when you started your program, you can call: Chris@82:

Chris@82: Chris@82:
Chris@82:
void fftw_mpi_cleanup(void);
Chris@82: 
Chris@82: Chris@82: Chris@82:

(This calls fftw_cleanup, so you need not call the serial Chris@82: cleanup routine too, although it is safe to do so.) After calling Chris@82: fftw_mpi_cleanup, all existing plans become undefined, and you Chris@82: should not attempt to execute or destroy them. You must call Chris@82: fftw_mpi_init again after fftw_mpi_cleanup if you want Chris@82: to resume using the MPI FFTW routines. Chris@82:

Chris@82: Chris@82: Chris@82: Chris@82: Chris@82: