annotate src/fftw-3.3.8/doc/html/Caveats-in-Using-Wisdom.html @ 167:bd3cc4d1df30

Add FFTW 3.3.8 source, and a Linux build
author Chris Cannam <cannam@all-day-breakfast.com>
date Tue, 19 Nov 2019 14:52:55 +0000
parents
children
rev   line source
cannam@167 1 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
cannam@167 2 <html>
cannam@167 3 <!-- This manual is for FFTW
cannam@167 4 (version 3.3.8, 24 May 2018).
cannam@167 5
cannam@167 6 Copyright (C) 2003 Matteo Frigo.
cannam@167 7
cannam@167 8 Copyright (C) 2003 Massachusetts Institute of Technology.
cannam@167 9
cannam@167 10 Permission is granted to make and distribute verbatim copies of this
cannam@167 11 manual provided the copyright notice and this permission notice are
cannam@167 12 preserved on all copies.
cannam@167 13
cannam@167 14 Permission is granted to copy and distribute modified versions of this
cannam@167 15 manual under the conditions for verbatim copying, provided that the
cannam@167 16 entire resulting derived work is distributed under the terms of a
cannam@167 17 permission notice identical to this one.
cannam@167 18
cannam@167 19 Permission is granted to copy and distribute translations of this manual
cannam@167 20 into another language, under the above conditions for modified versions,
cannam@167 21 except that this permission notice may be stated in a translation
cannam@167 22 approved by the Free Software Foundation. -->
cannam@167 23 <!-- Created by GNU Texinfo 6.3, http://www.gnu.org/software/texinfo/ -->
cannam@167 24 <head>
cannam@167 25 <title>FFTW 3.3.8: Caveats in Using Wisdom</title>
cannam@167 26
cannam@167 27 <meta name="description" content="FFTW 3.3.8: Caveats in Using Wisdom">
cannam@167 28 <meta name="keywords" content="FFTW 3.3.8: Caveats in Using Wisdom">
cannam@167 29 <meta name="resource-type" content="document">
cannam@167 30 <meta name="distribution" content="global">
cannam@167 31 <meta name="Generator" content="makeinfo">
cannam@167 32 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
cannam@167 33 <link href="index.html#Top" rel="start" title="Top">
cannam@167 34 <link href="Concept-Index.html#Concept-Index" rel="index" title="Concept Index">
cannam@167 35 <link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
cannam@167 36 <link href="Other-Important-Topics.html#Other-Important-Topics" rel="up" title="Other Important Topics">
cannam@167 37 <link href="FFTW-Reference.html#FFTW-Reference" rel="next" title="FFTW Reference">
cannam@167 38 <link href="Words-of-Wisdom_002dSaving-Plans.html#Words-of-Wisdom_002dSaving-Plans" rel="prev" title="Words of Wisdom-Saving Plans">
cannam@167 39 <style type="text/css">
cannam@167 40 <!--
cannam@167 41 a.summary-letter {text-decoration: none}
cannam@167 42 blockquote.indentedblock {margin-right: 0em}
cannam@167 43 blockquote.smallindentedblock {margin-right: 0em; font-size: smaller}
cannam@167 44 blockquote.smallquotation {font-size: smaller}
cannam@167 45 div.display {margin-left: 3.2em}
cannam@167 46 div.example {margin-left: 3.2em}
cannam@167 47 div.lisp {margin-left: 3.2em}
cannam@167 48 div.smalldisplay {margin-left: 3.2em}
cannam@167 49 div.smallexample {margin-left: 3.2em}
cannam@167 50 div.smalllisp {margin-left: 3.2em}
cannam@167 51 kbd {font-style: oblique}
cannam@167 52 pre.display {font-family: inherit}
cannam@167 53 pre.format {font-family: inherit}
cannam@167 54 pre.menu-comment {font-family: serif}
cannam@167 55 pre.menu-preformatted {font-family: serif}
cannam@167 56 pre.smalldisplay {font-family: inherit; font-size: smaller}
cannam@167 57 pre.smallexample {font-size: smaller}
cannam@167 58 pre.smallformat {font-family: inherit; font-size: smaller}
cannam@167 59 pre.smalllisp {font-size: smaller}
cannam@167 60 span.nolinebreak {white-space: nowrap}
cannam@167 61 span.roman {font-family: initial; font-weight: normal}
cannam@167 62 span.sansserif {font-family: sans-serif; font-weight: normal}
cannam@167 63 ul.no-bullet {list-style: none}
cannam@167 64 -->
cannam@167 65 </style>
cannam@167 66
cannam@167 67
cannam@167 68 </head>
cannam@167 69
cannam@167 70 <body lang="en">
cannam@167 71 <a name="Caveats-in-Using-Wisdom"></a>
cannam@167 72 <div class="header">
cannam@167 73 <p>
cannam@167 74 Previous: <a href="Words-of-Wisdom_002dSaving-Plans.html#Words-of-Wisdom_002dSaving-Plans" accesskey="p" rel="prev">Words of Wisdom-Saving Plans</a>, Up: <a href="Other-Important-Topics.html#Other-Important-Topics" accesskey="u" rel="up">Other Important Topics</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>
cannam@167 75 </div>
cannam@167 76 <hr>
cannam@167 77 <a name="Caveats-in-Using-Wisdom-1"></a>
cannam@167 78 <h3 class="section">3.4 Caveats in Using Wisdom</h3>
cannam@167 79 <a name="index-wisdom_002c-problems-with"></a>
cannam@167 80
cannam@167 81 <blockquote>
cannam@167 82 <i>
cannam@167 83 <p>For in much wisdom is much grief, and he that increaseth knowledge
cannam@167 84 increaseth sorrow.
cannam@167 85 </i>
cannam@167 86 [Ecclesiastes 1:18]
cannam@167 87 <a name="index-Ecclesiastes"></a>
cannam@167 88 </p></blockquote>
cannam@167 89
cannam@167 90 <a name="index-portability-1"></a>
cannam@167 91 <p>There are pitfalls to using wisdom, in that it can negate FFTW&rsquo;s
cannam@167 92 ability to adapt to changing hardware and other conditions. For
cannam@167 93 example, it would be perfectly possible to export wisdom from a
cannam@167 94 program running on one processor and import it into a program running
cannam@167 95 on another processor. Doing so, however, would mean that the second
cannam@167 96 program would use plans optimized for the first processor, instead of
cannam@167 97 the one it is running on.
cannam@167 98 </p>
cannam@167 99 <p>It should be safe to reuse wisdom as long as the hardware and program
cannam@167 100 binaries remain unchanged. (Actually, the optimal plan may change even
cannam@167 101 between runs of the same binary on identical hardware, due to
cannam@167 102 differences in the virtual memory environment, etcetera. Users
cannam@167 103 seriously interested in performance should worry about this problem,
cannam@167 104 too.) It is likely that, if the same wisdom is used for two
cannam@167 105 different program binaries, even running on the same machine, the
cannam@167 106 plans may be sub-optimal because of differing code alignments. It is
cannam@167 107 therefore wise to recreate wisdom every time an application is
cannam@167 108 recompiled. The more the underlying hardware and software changes
cannam@167 109 between the creation of wisdom and its use, the greater grows
cannam@167 110 the risk of sub-optimal plans.
cannam@167 111 </p>
cannam@167 112 <p>Nevertheless, if the choice is between using <code>FFTW_ESTIMATE</code> or
cannam@167 113 using possibly-suboptimal wisdom (created on the same machine, but for a
cannam@167 114 different binary), the wisdom is likely to be better. For this reason,
cannam@167 115 we provide a function to import wisdom from a standard system-wide
cannam@167 116 location (<code>/etc/fftw/wisdom</code> on Unix):
cannam@167 117 <a name="index-wisdom_002c-system_002dwide"></a>
cannam@167 118 </p>
cannam@167 119 <div class="example">
cannam@167 120 <pre class="example">int fftw_import_system_wisdom(void);
cannam@167 121 </pre></div>
cannam@167 122 <a name="index-fftw_005fimport_005fsystem_005fwisdom"></a>
cannam@167 123
cannam@167 124 <p>FFTW also provides a standalone program, <code>fftw-wisdom</code> (described
cannam@167 125 by its own <code>man</code> page on Unix) with which users can create wisdom,
cannam@167 126 e.g. for a canonical set of sizes to store in the system wisdom file.
cannam@167 127 See <a href="Wisdom-Utilities.html#Wisdom-Utilities">Wisdom Utilities</a>.
cannam@167 128 <a name="index-fftw_002dwisdom-utility"></a>
cannam@167 129 </p>
cannam@167 130 <hr>
cannam@167 131 <div class="header">
cannam@167 132 <p>
cannam@167 133 Previous: <a href="Words-of-Wisdom_002dSaving-Plans.html#Words-of-Wisdom_002dSaving-Plans" accesskey="p" rel="prev">Words of Wisdom-Saving Plans</a>, Up: <a href="Other-Important-Topics.html#Other-Important-Topics" accesskey="u" rel="up">Other Important Topics</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>
cannam@167 134 </div>
cannam@167 135
cannam@167 136
cannam@167 137
cannam@167 138 </body>
cannam@167 139 </html>