Introduce MPI communicator and make relevant parts MPI aware. Suggestion is to rely on FFTWs MPI parallelization initially.
Need to discuss which classes need to know about MPI. First discussion with Till resulted in the conclusion that Field collection should broker MPI communicator and FFT class should decide decomposition. CG solver also needs to know about MPI but probably does not need decomposition.
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | pastewka | T1888 MPI parallelization | ||
| Resolved | pastewka | T1911 FFTW MPI Engine | ||
| Resolved | pastewka | T1912 PFFT Engine | ||
| Open | pastewka | T1913 P3DFFT Engine | ||
| Resolved | pastewka | T1914 MPI parallel solver | ||
| Resolved | pastewka | T1931 Expose MPI parallelism to Python | ||
| Resolved | pastewka | T1933 Thin Python wrapper that hides extraction of handles from mpi4py communicator object | ||
| Resolved | pastewka | T1944 Python bindings for Projection classes using different FFT engines | ||
| Open | pastewka | T1915 AccFFT Engine | ||
| Resolved | pastewka | T1916 Add abstraction layer for communicator |