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