|
1 | 1 | .\" -*- nroff -*- |
2 | 2 | .\" Copyright 2006-2008 Sun Microsystems, Inc. |
3 | 3 | .\" Copyright (c) 1996 Thinking Machines Corporation |
4 | | -.\" Copyright (c) 2010-2015 Cisco Systems, Inc. All rights reserved. |
| 4 | +.\" Copyright (c) 2010-2020 Cisco Systems, Inc. All rights reserved. |
| 5 | +.\" Copyright (c) 2020 Google, LLC. All rights reserved. |
5 | 6 | .\" $COPYRIGHT$ |
6 | 7 | .TH MPI_Init_thread 3 "#OMPI_DATE#" "#PACKAGE_VERSION#" "#PACKAGE_NAME#" |
7 | 8 | . |
@@ -92,7 +93,7 @@ with no restrictions. |
92 | 93 | . |
93 | 94 | .PP |
94 | 95 | The level of thread support available to the program is set in |
95 | | -\fIprovided\fP, except in C++, where it is the return value of the |
| 96 | +\fIprovided\fP, except in the C++ binding, where it is the return value of the |
96 | 97 | function. In Open MPI, the value is dependent on how the library was |
97 | 98 | configured and built. Note that there is no guarantee that |
98 | 99 | \fIprovided\fP will be greater than or equal to \fIrequired\fP. |
@@ -135,52 +136,27 @@ opening files, reading standard input, or writing to standard output. |
135 | 136 | . |
136 | 137 | .SH MPI_THREAD_MULTIPLE Support |
137 | 138 | . |
138 | | -MPI_THREAD_MULTIPLE support is included if Open MPI was configured |
139 | | -with the --enable-mpi-thread-multiple configure switch. You can check the |
| 139 | +MPI_THREAD_MULTIPLE support is included if the environment in which |
| 140 | +Open MPI was built supports threading. You can check the |
140 | 141 | output of |
141 | 142 | .BR ompi_info (1) |
142 | 143 | to see if Open MPI has MPI_THREAD_MULTIPLE support: |
143 | 144 | . |
144 | 145 | .PP |
145 | 146 | .nf |
146 | | -shell$ ompi_info | grep -i thread |
147 | | - Thread support: posix (mpi: yes, progress: no) |
| 147 | +shell$ ompi_info | grep "Thread support" |
| 148 | + Thread support: posix (MPI_THREAD_MULTIPLE: yes, OPAL support: yes, OMPI progress: no, Event lib: yes) |
148 | 149 | shell$ |
149 | 150 | .fi |
150 | 151 | . |
151 | 152 | .PP |
152 | | -The "mpi: yes" portion of the above output indicates that Open MPI was |
153 | | -compiled with MPI_THREAD_MULTIPLE support. |
| 153 | +The "MPI_THREAD_MULTIPLE: yes" portion of the above output indicates |
| 154 | +that Open MPI was compiled with MPI_THREAD_MULTIPLE support. |
154 | 155 | . |
155 | 156 | .PP |
156 | | -Note that MPI_THREAD_MULTIPLE support is only lightly tested. It |
157 | | -likely does not work for thread-intensive applications. Also note |
158 | | -that |
159 | | -.I only |
160 | | -the MPI point-to-point communication functions for the BTL's listed |
161 | | -below are considered thread safe. Other support functions (e.g., MPI |
162 | | -attributes) have not been certified as safe when simultaneously used |
163 | | -by multiple threads. |
164 | | -. |
165 | | -.PP |
166 | | -.nf |
167 | | - tcp |
168 | | - sm |
169 | | - mx |
170 | | - elan |
171 | | - self |
172 | | -.fi |
173 | | -. |
174 | | -.PP |
175 | | -Note that Open MPI's thread support is in a fairly early stage; the |
176 | | -above devices are likely to |
177 | | -.IR work , |
178 | | -but the latency is likely to be fairly high. Specifically, efforts so |
179 | | -far have concentrated on |
180 | | -.IR correctness , |
181 | | -not |
182 | | -.I performance |
183 | | -(yet). |
| 157 | +Note that there is a small performance penalty for using |
| 158 | +MPI_THREAD_MULTIPLE support; latencies for short messages will be |
| 159 | +higher as compared to when using MPI_THREAD_SINGLE, for example. |
184 | 160 | . |
185 | 161 | . |
186 | 162 | .SH ERRORS |
|
0 commit comments