Blame man/man3/PAPI_unregister_thread.3

Packit Service a1973e
.TH "PAPI_unregister_thread" 3 "Mon Dec 18 2017" "Version 5.6.0.0" "PAPI" \" -*- nroff -*-
Packit Service a1973e
.ad l
Packit Service a1973e
.nh
Packit Service a1973e
.SH NAME
Packit Service a1973e
PAPI_unregister_thread \- 
Packit Service a1973e
.PP
Packit Service a1973e
Notify PAPI that a thread has 'disappeared'\&.  
Packit Service a1973e
Packit Service a1973e
.SH SYNOPSIS
Packit Service a1973e
.br
Packit Service a1973e
.PP
Packit Service a1973e
.SH "Detailed Description"
Packit Service a1973e
.PP 
Packit Service a1973e
Packit Service a1973e
.PP
Packit Service a1973e
\fBReturn values:\fP
Packit Service a1973e
.RS 4
Packit Service a1973e
\fIPAPI_ENOMEM\fP Space could not be allocated to store the new thread information\&. 
Packit Service a1973e
.br
Packit Service a1973e
\fIPAPI_ESYS\fP A system or C library call failed inside PAPI, see the errno variable\&. 
Packit Service a1973e
.br
Packit Service a1973e
\fIPAPI_ECMP\fP Hardware counters for this thread could not be initialized\&.
Packit Service a1973e
.RE
Packit Service a1973e
.PP
Packit Service a1973e
\fBPAPI_unregister_thread\fP should be called when the user wants to shutdown a particular thread and free the associated thread ID\&. THIS IS IMPORTANT IF YOUR THREAD LIBRARY REUSES THE SAME THREAD ID FOR A NEW KERNEL LWP\&. OpenMP does this\&. OpenMP parallel regions, if separated by a call to omp_set_num_threads() will often kill off the underlying kernel LWPs and then start new ones for the next region\&. However, omp_get_thread_id() does not reflect this, as the thread IDs for the new LWPs will be the same as the old LWPs\&. PAPI needs to know that the underlying LWP has changed so it can set up the counters for that new thread\&. This is accomplished by calling this function\&. 
Packit Service a1973e
Packit Service a1973e
.SH "Author"
Packit Service a1973e
.PP 
Packit Service a1973e
Generated automatically by Doxygen for PAPI from the source code\&.