We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If we represent tensors in the same memory footprint, is it correct that we can call cuDNN, MKL, and Neon to operate tensors on various devices?
The text was updated successfully, but these errors were encountered:
OK, one cent is that BLAS just defined some very primitive and frequently used operations. But all these toolkits are much more powerful than BLAS.
Sorry, something went wrong.
memory layout should be specified if using third-party libs, like MKL, cuDNN, OpenBlas. All of them supports column major, thus that's not a problem.
In Majel, the internal implementation of gemm(Array, ...) also invoked cublas_gemm(Array.ptr()) and MKL's cblas_gemm(Array.ptr()).
gemm(Array, ...)
cublas_gemm(Array.ptr())
MKL's cblas_gemm(Array.ptr())
@wangkuiyi
Thus, it's definitely compatible.
Thanks to @gangliao
wangkuiyi
No branches or pull requests
If we represent tensors in the same memory footprint, is it correct that we can call cuDNN, MKL, and Neon to operate tensors on various devices?
The text was updated successfully, but these errors were encountered: