annotate fft/fftw/fftw-3.3.4/doc/html/Using-MPI-Plans.html @ 40:223f770b5341 kissfft-double tip

Try a double-precision kissfft
author Chris Cannam
date Wed, 07 Sep 2016 10:40:32 +0100
parents 26056e866c29
children
rev   line source
Chris@19 1 <html lang="en">
Chris@19 2 <head>
Chris@19 3 <title>Using MPI Plans - FFTW 3.3.4</title>
Chris@19 4 <meta http-equiv="Content-Type" content="text/html">
Chris@19 5 <meta name="description" content="FFTW 3.3.4">
Chris@19 6 <meta name="generator" content="makeinfo 4.13">
Chris@19 7 <link title="Top" rel="start" href="index.html#Top">
Chris@19 8 <link rel="up" href="FFTW-MPI-Reference.html#FFTW-MPI-Reference" title="FFTW MPI Reference">
Chris@19 9 <link rel="prev" href="MPI-Initialization.html#MPI-Initialization" title="MPI Initialization">
Chris@19 10 <link rel="next" href="MPI-Data-Distribution-Functions.html#MPI-Data-Distribution-Functions" title="MPI Data Distribution Functions">
Chris@19 11 <link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
Chris@19 12 <!--
Chris@19 13 This manual is for FFTW
Chris@19 14 (version 3.3.4, 20 September 2013).
Chris@19 15
Chris@19 16 Copyright (C) 2003 Matteo Frigo.
Chris@19 17
Chris@19 18 Copyright (C) 2003 Massachusetts Institute of Technology.
Chris@19 19
Chris@19 20 Permission is granted to make and distribute verbatim copies of
Chris@19 21 this manual provided the copyright notice and this permission
Chris@19 22 notice are preserved on all copies.
Chris@19 23
Chris@19 24 Permission is granted to copy and distribute modified versions of
Chris@19 25 this manual under the conditions for verbatim copying, provided
Chris@19 26 that the entire resulting derived work is distributed under the
Chris@19 27 terms of a permission notice identical to this one.
Chris@19 28
Chris@19 29 Permission is granted to copy and distribute translations of this
Chris@19 30 manual into another language, under the above conditions for
Chris@19 31 modified versions, except that this permission notice may be
Chris@19 32 stated in a translation approved by the Free Software Foundation.
Chris@19 33 -->
Chris@19 34 <meta http-equiv="Content-Style-Type" content="text/css">
Chris@19 35 <style type="text/css"><!--
Chris@19 36 pre.display { font-family:inherit }
Chris@19 37 pre.format { font-family:inherit }
Chris@19 38 pre.smalldisplay { font-family:inherit; font-size:smaller }
Chris@19 39 pre.smallformat { font-family:inherit; font-size:smaller }
Chris@19 40 pre.smallexample { font-size:smaller }
Chris@19 41 pre.smalllisp { font-size:smaller }
Chris@19 42 span.sc { font-variant:small-caps }
Chris@19 43 span.roman { font-family:serif; font-weight:normal; }
Chris@19 44 span.sansserif { font-family:sans-serif; font-weight:normal; }
Chris@19 45 --></style>
Chris@19 46 </head>
Chris@19 47 <body>
Chris@19 48 <div class="node">
Chris@19 49 <a name="Using-MPI-Plans"></a>
Chris@19 50 <p>
Chris@19 51 Next:&nbsp;<a rel="next" accesskey="n" href="MPI-Data-Distribution-Functions.html#MPI-Data-Distribution-Functions">MPI Data Distribution Functions</a>,
Chris@19 52 Previous:&nbsp;<a rel="previous" accesskey="p" href="MPI-Initialization.html#MPI-Initialization">MPI Initialization</a>,
Chris@19 53 Up:&nbsp;<a rel="up" accesskey="u" href="FFTW-MPI-Reference.html#FFTW-MPI-Reference">FFTW MPI Reference</a>
Chris@19 54 <hr>
Chris@19 55 </div>
Chris@19 56
Chris@19 57 <h4 class="subsection">6.12.3 Using MPI Plans</h4>
Chris@19 58
Chris@19 59 <p>Once an MPI plan is created, you can execute and destroy it using
Chris@19 60 <code>fftw_execute</code>, <code>fftw_destroy_plan</code>, and the other functions
Chris@19 61 in the serial interface that operate on generic plans (see <a href="Using-Plans.html#Using-Plans">Using Plans</a>).
Chris@19 62
Chris@19 63 <p><a name="index-collective-function-441"></a><a name="index-MPI-communicator-442"></a>The <code>fftw_execute</code> and <code>fftw_destroy_plan</code> functions, applied to
Chris@19 64 MPI plans, are <em>collective</em> calls: they must be called for all processes
Chris@19 65 in the communicator that was used to create the plan.
Chris@19 66
Chris@19 67 <p><a name="index-new_002darray-execution-443"></a>You must <em>not</em> use the serial new-array plan-execution functions
Chris@19 68 <code>fftw_execute_dft</code> and so on (see <a href="New_002darray-Execute-Functions.html#New_002darray-Execute-Functions">New-array Execute Functions</a>) with MPI plans. Such functions are specialized to the
Chris@19 69 problem type, and there are specific new-array execute functions for MPI plans:
Chris@19 70
Chris@19 71 <p><a name="index-fftw_005fmpi_005fexecute_005fdft-444"></a><a name="index-fftw_005fmpi_005fexecute_005fdft_005fr2c-445"></a><a name="index-fftw_005fmpi_005fexecute_005fdft_005fc2r-446"></a><a name="index-fftw_005fmpi_005fexecute_005fr2r-447"></a>
Chris@19 72 <pre class="example"> void fftw_mpi_execute_dft(fftw_plan p, fftw_complex *in, fftw_complex *out);
Chris@19 73 void fftw_mpi_execute_dft_r2c(fftw_plan p, double *in, fftw_complex *out);
Chris@19 74 void fftw_mpi_execute_dft_c2r(fftw_plan p, fftw_complex *in, double *out);
Chris@19 75 void fftw_mpi_execute_r2r(fftw_plan p, double *in, double *out);
Chris@19 76 </pre>
Chris@19 77 <p><a name="index-alignment-448"></a><a name="index-fftw_005fmalloc-449"></a>These functions have the same restrictions as those of the serial
Chris@19 78 new-array execute functions. They are <em>always</em> safe to apply to
Chris@19 79 the <em>same</em> <code>in</code> and <code>out</code> arrays that were used to
Chris@19 80 create the plan. They can only be applied to new arrarys if those
Chris@19 81 arrays have the same types, dimensions, in-placeness, and alignment as
Chris@19 82 the original arrays, where the best way to ensure the same alignment
Chris@19 83 is to use FFTW's <code>fftw_malloc</code> and related allocation functions
Chris@19 84 for all arrays (see <a href="Memory-Allocation.html#Memory-Allocation">Memory Allocation</a>). Note that distributed
Chris@19 85 transposes (see <a href="FFTW-MPI-Transposes.html#FFTW-MPI-Transposes">FFTW MPI Transposes</a>) use
Chris@19 86 <code>fftw_mpi_execute_r2r</code>, since they count as rank-zero r2r plans
Chris@19 87 from FFTW's perspective.
Chris@19 88
Chris@19 89 </body></html>
Chris@19 90