The general form of the discrete Fourier transform is
for k_{l} = 0, ... n_{l}1 (
l = 1, ..., d), where σ is a scale factor, δ = 1 for the forward transform, and δ = +1 for the inverse (backward) transform. In the forward transform, the input (periodic) sequence {w_{j1, j2, ..., jd}}
belongs to the set of complexvalued sequences and realvalued sequences. Respective domains for the backward transform are represented by complexvalued sequences and complexvalued conjugateeven sequences.
The Intel® Math Kernel Library (Intel® MKL) provides an interface for computing a discrete Fourier transform through the fast Fourier transform algorithm. The manual describes the following implementations of the fast Fourier transform functions available in Intel MKL:
 Fast Fourier transform (FFT) functions for singleprocessor or sharedmemory systems (see FFT Functions)
 Cluster FFT functions for distributedmemory architectures (available with Intel® MKL for the Linux* and Windows* operating systems only)
Note
Intel MKL also supports the FFTW3* interfaces to the fast Fourier transform functionality for shared memory paradigm (SMP) systems.
Both FFT and Cluster FFT functions compute an FFT in five steps:

Allocate a fresh descriptor for the problem with a call to the DftiCreateDescriptor or DftiCreateDescriptorDM function. The descriptor captures the configuration of the transform, such as the dimensionality (or rank), sizes, number of transforms, memory layout of the input/output data (defined by strides), and scaling factors. Many of the configuration settings are assigned default values in this call which you might need to modify in your application.

Optionally adjust the descriptor configuration with a call to the DftiSetValue or DftiSetValueDM function as needed. Typically, you must carefully define the data storage layout for an FFT or the data distribution among processes for a Cluster FFT. The configuration settings of the descriptor, such as the default values, can be obtained with the DftiGetValue or DftiGetValueDM function.

Commit the descriptor with a call to the DftiCommitDescriptor or DftiCommitDescriptorDM function, that is, make the descriptor ready for the transform computation. Once the descriptor is committed, the parameters of the transform, such as the type and number of transforms, strides and distances, the type and storage layout of the data, and so on, are "frozen" in the descriptor.

Compute the transform with a call to the DftiComputeForward/DftiComputeBackward or DftiComputeForwardDM/DftiComputeBackwardDM functions as many times as needed. Because the descriptor is defined and committed separately, all that the compute functions do is take the input and output data and compute the transform as defined. To modify any configuration parameters for another call to a compute function, use DftiSetValue followed by DftiCommitDescriptor (DftiSetValueDM followed by DftiCommitDescriptorDM) or create and commit another descriptor.
 Deallocate the descriptor with a call to the DftiFreeDescriptor or DftiFreeDescriptorDM function. This returns the memory internally consumed by the descriptor to the operating system.
All the above functions return an integer status value, which is zero upon successful completion of the operation. You can interpret a nonzero status with the help of the DftiErrorClass or DftiErrorMessage function.
The FFT functions support lengths with arbitrary factors. You can improve performance of the Intel MKL FFT if the length of your data vector permits factorization into powers of optimized radices. See the Intel MKL User's Guide for specific radices supported efficiently.
Note
The FFT functions assume the Cartesian representation of complex data (that is, the real and imaginary parts define a complex number). The Intel MKL Vector Mathematical Functions provide efficient tools for conversion to and from polar representation (see Example "Conversion from Cartesian to polar representation of complex data" and Example "Conversion from polar to Cartesian representation of complex data").
Intel's compilers may or may not optimize to the same degree for nonIntel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessordependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice. Notice revision #20110804 