table of contents
other versions
- jessie 5.3.2-2
- jessie-backports 5.5.1-1~bpo8+1
- stretch 5.5.1-2
- testing 5.6.0+git99-gd5a1a9ae2-1
- unstable 5.7.0-1
PAPI_unregister_thread(3) | PAPI | PAPI_unregister_thread(3) |
NAME¶
PAPI_unregister_thread - Notify PAPI that a thread has 'disappeared'.SYNOPSIS¶
Detailed Description¶
Return values:PAPI_ENOMEM Space could not be allocated to store
the new thread information.
PAPI_ESYS A system or C library call failed inside PAPI, see the errno
variable.
PAPI_ECMP Hardware counters for this thread could not be
initialized.
PAPI_unregister_thread 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.
Author¶
Generated automatically by Doxygen for PAPI from the source code.Thu Nov 17 2016 | Version 5.5.1.0 |