allows to use fair dispatch in Intel MKL #448
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If configured with
IntelMKL_FAIR_DISPATCH=ONwill try to override Intel-centric processor detection in Intel MKL. Until MKL 2020.1 it was possible to use the undocumented environment variableMKL_DEBUG_CPU_TYPE(e.g. set it to5to force the use of AVX2 instruction set), but this variable no longer works. This adds the code from https://www.agner.org/optimize/intel_dispatch_patch.zip to try forcing the use of fair dispatch. Seems to work successfully on the Tinkercliffs cluster with AMD Rome processors.P.S. see also http://public.clu2.fastmail.us.user.fm/icc_cpu_dispatch.html