I'm testing the behaviour of the OMP_WAIT_POLICY environment variable with an application that performs several millions of OpenMP barriers. However, it takes the same time indepently from the "active" or "passive" value. I've studied an Amplifier trace and it's pretty similar, where the most expensive routine is __kmp_wait_sleep, and in second place __kmp_static_yield, even when OMP_WAIT_POLICY=active. It seems like the runtime is always running the passive policy.
I run in native mode, but I observed the same behavior running on the host (without using MIC).
I'm using ICC 13.0.0
Is there any issue?