-
Notifications
You must be signed in to change notification settings - Fork 12.2k
[SYCL] Add oneDNN primitive support #9091
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's great to involve the oneDNN in SYCL backend.
-
If oneDNN is detected, oneMKL won't be used in whole code.
Is it right? -
Please update the SYCL.md with oneMKL and oneDNN dependence info.
|
* add onednn * add sycl_f16 * add dnnl stream * add engine map * use dnnl for intel only * use fp16fp16fp16 * update doc
* add onednn * add sycl_f16 * add dnnl stream * add engine map * use dnnl for intel only * use fp16fp16fp16 * update doc
Interesting. I wonder whether this thing, similar to OneDNN https://github.com/amd/ZenDNN could be integrated into SYCL backend. |
* add onednn * add sycl_f16 * add dnnl stream * add engine map * use dnnl for intel only * use fp16fp16fp16 * update doc
This thing is CPU only and is not intended to be used as standalone software. oneDNN will cover AMD client and server CPUs nicely if necessary. |
oneMKL and oneDNN almost share the same GPU kernels, but oneDNN has better compatibility.
llama-bench on A750:
on A770m, the master branch crashed with GGML_SYCL_F16=ON, this branch with oneDNN can run it.
Ultra-155H, MKL throws this error: