Chris@19: Chris@19:
Chris@19:Chris@19: Next: Using MPI Plans, Chris@19: Previous: MPI Files and Data Types, Chris@19: Up: FFTW MPI Reference Chris@19:
Before calling any other FFTW MPI (‘fftw_mpi_’) function, and Chris@19: before importing any wisdom for MPI problems, you must call: Chris@19: Chris@19:
void fftw_mpi_init(void); Chris@19:Chris@19:
If FFTW threads support is used, however, fftw_mpi_init
should
Chris@19: be called after fftw_init_threads
(see Combining MPI and Threads). Calling fftw_mpi_init
additional times (before
Chris@19: fftw_mpi_cleanup
) has no effect.
Chris@19:
Chris@19:
If you want to deallocate all persistent data and reset FFTW to the Chris@19: pristine state it was in when you started your program, you can call: Chris@19: Chris@19:
void fftw_mpi_cleanup(void); Chris@19:Chris@19:
(This calls fftw_cleanup
, so you need not call the serial
Chris@19: cleanup routine too, although it is safe to do so.) After calling
Chris@19: fftw_mpi_cleanup
, all existing plans become undefined, and you
Chris@19: should not attempt to execute or destroy them. You must call
Chris@19: fftw_mpi_init
again after fftw_mpi_cleanup
if you want
Chris@19: to resume using the MPI FFTW routines.
Chris@19:
Chris@19:
Chris@19: