-
Notifications
You must be signed in to change notification settings - Fork 284
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
enable MKL-DNN/oneDNN usage for aarch64 CPUs in TensorFlow 2.5+ #2574
enable MKL-DNN/oneDNN usage for aarch64 CPUs in TensorFlow 2.5+ #2574
Conversation
add logging for auto-enabling use of MKL-DNN for TensorFlow
Test report by @boegel Overview of tested easyconfigs (in order)
Build succeeded for 0 out of 2 (2 easyconfigs in total) |
Any cgroup stuff maybe? |
Or perhaps lack of memory... This was on a c6g.2xlarge AWS instance (8 cores, 16GB of RAM), which is perhaps a bit on the light side to build TensorFlow from source (using 8 cores)? I'll try again on a fatter node (or using less cores). |
Test report by @boegel Overview of tested easyconfigs (in order)
Build succeeded for 0 out of 2 (2 easyconfigs in total) |
@boegel Bug in TF with excluding based on arch and a config flag leading to ambigious, yet same select cases: https://github.com/tensorflow/tensorflow/blob/72fd2bfa42a8ad909baf8d2b7b674563d256514d/tensorflow/core/kernels/BUILD#L3028-L3034 (arm_any and no_mkldnn_contraction_kernel triggers) |
@Flamefire It's not clear to me what's going wrong here, so I'm not sure what to put in the issue. Also, I have very little bandwidth to follow up on it... Does it basically mean that the |
Did that: tensorflow/tensorflow#52027 More or less: yes. However for ARM we might want to use |
Closing as this isn't actually enabling mklDNN/oneDNN. See #2577 and https://groups.google.com/a/tensorflow.org/g/build/c/RZhgZst-fgQ |
(created using
eb --new-pr
)