Thread pool libgomp (openmp)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



When changing the number of threads dynamically in OpenMP, I've seen that
if the next region has fewer threads than the previous, the exceed is left
to die. So, in the future, if another region needs more threads is
necessary calling pthread_create() again. Why doesn't libgomp maintains the
exceed threads in the pool to reuse case necessary?



[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux