Le 03/05/2019 à 17:57, Jed Brown a écrit : > >>> The library is then free to use constructs like omp taskgroup/taskloop >>> as granularity warrants; it will never utilize threads that the >>> application didn't explicitly give it. >> >> I don't think we're planning to use OpenMP in Arrow, though Wes probably >> has a better answer. > > I was just using it to demonstrate the semantic. Regardless of what > Arrow uses internally, there will be a cohort of users who are > interested in using Arrow with OpenMP.
I know next to nothing about OpenMP, but we have some code that's supposed to enable cooperation with OpenMP here: https://github.com/apache/arrow/blob/master/cpp/src/arrow/util/thread-pool.cc#L268 If that doesn't work as intended, feel free to open an issue and describe the problem. Regards Antoine.
