annotate src/fftw-3.3.8/doc/html/Multi_002dthreaded-FFTW.html @ 83:ae30d91d2ffe

Replace these with versions built using an older toolset (so as to avoid ABI compatibilities when linking on Ubuntu 14.04 for packaging purposes)
author Chris Cannam
date Fri, 07 Feb 2020 11:51:13 +0000
parents d0c2a83c1364
children
rev   line source
Chris@82 1 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
Chris@82 2 <html>
Chris@82 3 <!-- This manual is for FFTW
Chris@82 4 (version 3.3.8, 24 May 2018).
Chris@82 5
Chris@82 6 Copyright (C) 2003 Matteo Frigo.
Chris@82 7
Chris@82 8 Copyright (C) 2003 Massachusetts Institute of Technology.
Chris@82 9
Chris@82 10 Permission is granted to make and distribute verbatim copies of this
Chris@82 11 manual provided the copyright notice and this permission notice are
Chris@82 12 preserved on all copies.
Chris@82 13
Chris@82 14 Permission is granted to copy and distribute modified versions of this
Chris@82 15 manual under the conditions for verbatim copying, provided that the
Chris@82 16 entire resulting derived work is distributed under the terms of a
Chris@82 17 permission notice identical to this one.
Chris@82 18
Chris@82 19 Permission is granted to copy and distribute translations of this manual
Chris@82 20 into another language, under the above conditions for modified versions,
Chris@82 21 except that this permission notice may be stated in a translation
Chris@82 22 approved by the Free Software Foundation. -->
Chris@82 23 <!-- Created by GNU Texinfo 6.3, http://www.gnu.org/software/texinfo/ -->
Chris@82 24 <head>
Chris@82 25 <title>FFTW 3.3.8: Multi-threaded FFTW</title>
Chris@82 26
Chris@82 27 <meta name="description" content="FFTW 3.3.8: Multi-threaded FFTW">
Chris@82 28 <meta name="keywords" content="FFTW 3.3.8: Multi-threaded FFTW">
Chris@82 29 <meta name="resource-type" content="document">
Chris@82 30 <meta name="distribution" content="global">
Chris@82 31 <meta name="Generator" content="makeinfo">
Chris@82 32 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Chris@82 33 <link href="index.html#Top" rel="start" title="Top">
Chris@82 34 <link href="Concept-Index.html#Concept-Index" rel="index" title="Concept Index">
Chris@82 35 <link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
Chris@82 36 <link href="index.html#Top" rel="up" title="Top">
Chris@82 37 <link href="Installation-and-Supported-Hardware_002fSoftware.html#Installation-and-Supported-Hardware_002fSoftware" rel="next" title="Installation and Supported Hardware/Software">
Chris@82 38 <link href="Multi_002ddimensional-Transforms.html#Multi_002ddimensional-Transforms" rel="prev" title="Multi-dimensional Transforms">
Chris@82 39 <style type="text/css">
Chris@82 40 <!--
Chris@82 41 a.summary-letter {text-decoration: none}
Chris@82 42 blockquote.indentedblock {margin-right: 0em}
Chris@82 43 blockquote.smallindentedblock {margin-right: 0em; font-size: smaller}
Chris@82 44 blockquote.smallquotation {font-size: smaller}
Chris@82 45 div.display {margin-left: 3.2em}
Chris@82 46 div.example {margin-left: 3.2em}
Chris@82 47 div.lisp {margin-left: 3.2em}
Chris@82 48 div.smalldisplay {margin-left: 3.2em}
Chris@82 49 div.smallexample {margin-left: 3.2em}
Chris@82 50 div.smalllisp {margin-left: 3.2em}
Chris@82 51 kbd {font-style: oblique}
Chris@82 52 pre.display {font-family: inherit}
Chris@82 53 pre.format {font-family: inherit}
Chris@82 54 pre.menu-comment {font-family: serif}
Chris@82 55 pre.menu-preformatted {font-family: serif}
Chris@82 56 pre.smalldisplay {font-family: inherit; font-size: smaller}
Chris@82 57 pre.smallexample {font-size: smaller}
Chris@82 58 pre.smallformat {font-family: inherit; font-size: smaller}
Chris@82 59 pre.smalllisp {font-size: smaller}
Chris@82 60 span.nolinebreak {white-space: nowrap}
Chris@82 61 span.roman {font-family: initial; font-weight: normal}
Chris@82 62 span.sansserif {font-family: sans-serif; font-weight: normal}
Chris@82 63 ul.no-bullet {list-style: none}
Chris@82 64 -->
Chris@82 65 </style>
Chris@82 66
Chris@82 67
Chris@82 68 </head>
Chris@82 69
Chris@82 70 <body lang="en">
Chris@82 71 <a name="Multi_002dthreaded-FFTW"></a>
Chris@82 72 <div class="header">
Chris@82 73 <p>
Chris@82 74 Next: <a href="Distributed_002dmemory-FFTW-with-MPI.html#Distributed_002dmemory-FFTW-with-MPI" accesskey="n" rel="next">Distributed-memory FFTW with MPI</a>, Previous: <a href="FFTW-Reference.html#FFTW-Reference" accesskey="p" rel="prev">FFTW Reference</a>, Up: <a href="index.html#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html#Concept-Index" title="Index" rel="index">Index</a>]</p>
Chris@82 75 </div>
Chris@82 76 <hr>
Chris@82 77 <a name="Multi_002dthreaded-FFTW-1"></a>
Chris@82 78 <h2 class="chapter">5 Multi-threaded FFTW</h2>
Chris@82 79
Chris@82 80 <a name="index-parallel-transform"></a>
Chris@82 81 <p>In this chapter we document the parallel FFTW routines for
Chris@82 82 shared-memory parallel hardware. These routines, which support
Chris@82 83 parallel one- and multi-dimensional transforms of both real and
Chris@82 84 complex data, are the easiest way to take advantage of multiple
Chris@82 85 processors with FFTW. They work just like the corresponding
Chris@82 86 uniprocessor transform routines, except that you have an extra
Chris@82 87 initialization routine to call, and there is a routine to set the
Chris@82 88 number of threads to employ. Any program that uses the uniprocessor
Chris@82 89 FFTW can therefore be trivially modified to use the multi-threaded
Chris@82 90 FFTW.
Chris@82 91 </p>
Chris@82 92 <p>A shared-memory machine is one in which all CPUs can directly access
Chris@82 93 the same main memory, and such machines are now common due to the
Chris@82 94 ubiquity of multi-core CPUs. FFTW&rsquo;s multi-threading support allows
Chris@82 95 you to utilize these additional CPUs transparently from a single
Chris@82 96 program. However, this does not necessarily translate into
Chris@82 97 performance gains&mdash;when multiple threads/CPUs are employed, there is
Chris@82 98 an overhead required for synchronization that may outweigh the
Chris@82 99 computatational parallelism. Therefore, you can only benefit from
Chris@82 100 threads if your problem is sufficiently large.
Chris@82 101 <a name="index-shared_002dmemory"></a>
Chris@82 102 <a name="index-threads"></a>
Chris@82 103 </p>
Chris@82 104 <table class="menu" border="0" cellspacing="0">
Chris@82 105 <tr><td align="left" valign="top">&bull; <a href="Installation-and-Supported-Hardware_002fSoftware.html#Installation-and-Supported-Hardware_002fSoftware" accesskey="1">Installation and Supported Hardware/Software</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
Chris@82 106 </td></tr>
Chris@82 107 <tr><td align="left" valign="top">&bull; <a href="Usage-of-Multi_002dthreaded-FFTW.html#Usage-of-Multi_002dthreaded-FFTW" accesskey="2">Usage of Multi-threaded FFTW</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
Chris@82 108 </td></tr>
Chris@82 109 <tr><td align="left" valign="top">&bull; <a href="How-Many-Threads-to-Use_003f.html#How-Many-Threads-to-Use_003f" accesskey="3">How Many Threads to Use?</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
Chris@82 110 </td></tr>
Chris@82 111 <tr><td align="left" valign="top">&bull; <a href="Thread-safety.html#Thread-safety" accesskey="4">Thread safety</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
Chris@82 112 </td></tr>
Chris@82 113 </table>
Chris@82 114
Chris@82 115
Chris@82 116
Chris@82 117
Chris@82 118 </body>
Chris@82 119 </html>