Query: papi_thread_init
OS: centos
Section: 3
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
PAPI_thread_init(3) PAPI PAPI_thread_init(3)NAMEPAPI_thread_init - Initialize thread support in the PAPI library.SYNOPSISDetailed Description @param *id_fn Pointer to a function that returns current thread ID. PAPI_thread_init initializes thread support in the PAPI library. Applications that make no use of threads do not need to call this routine. This function MUST return a UNIQUE thread ID for every new thread/LWP created. The OpenMP call omp_get_thread_num() violates this rule, as the underlying LWPs may have been killed off by the run-time system or by a call to omp_set_num_threads() . In that case, it may still possible to use omp_get_thread_num() in conjunction with PAPI_unregister_thread() when the OpenMP thread has finished. However it is much better to use the underlying thread subsystem's call, which is pthread_self() on Linux platforms. if ( PAPI_thread_init(pthread_self) != PAPI_OK ) exit(1); * See Also: PAPI_register_thread PAPI_unregister_thread PAPI_get_thr_specific PAPI_set_thr_specific PAPI_thread_id PAPI_list_threads Author Generated automatically by Doxygen for PAPI from the source code. Version 5.2.0.0 Tue Jun 17 2014 PAPI_thread_init(3)
Related Man Pages |
---|
papi_attach(3) - centos |
papi_detach(3) - centos |
papi_event_name_to_code(3) - centos |
papi_is_initialized(3) - centos |
papi_reset(3) - centos |
Similar Topics in the Unix Linux Community |
---|
Is UNIX an open source OS ? |
CentOS7 restoring file capabilities |
Unsure why access time on a directory change isn't changing |
CentOS 6 ran out of space, need to reclaim it |
Controlling user input |