You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know this maybe beyond the scope of this little project, but there's quite often other blas/mkl/omp-related variables that are set together, for instance MKL_DYNAMIC and OMP_DYNAMIC - which is directly related to thread allocation - any chance of supporting those?
At the very least, being able to call (and then restore back) omp_get_dynamic() / omp_set_dynamic() would be nice, for both libiomp/libgomp.
The text was updated successfully, but these errors were encountered:
I'm not sure it would fit nicely in threadpoolctl.thread_limits, since this is specific to OpenMP. But maybe through a different, more polyvalent, context manager.
I don't think that the default output of threadpool_info should display all possible threadpool status functions, but maybe we could add a parameter to enable that.
I know this maybe beyond the scope of this little project, but there's quite often other blas/mkl/omp-related variables that are set together, for instance
MKL_DYNAMIC
andOMP_DYNAMIC
- which is directly related to thread allocation - any chance of supporting those?At the very least, being able to call (and then restore back)
omp_get_dynamic()
/omp_set_dynamic()
would be nice, for both libiomp/libgomp.The text was updated successfully, but these errors were encountered: