Skip to content
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

[Tracking] OneAPI Packages #367722

Open
4 of 21 tasks
arunoruto opened this issue Dec 23, 2024 · 4 comments
Open
4 of 21 tasks

[Tracking] OneAPI Packages #367722

arunoruto opened this issue Dec 23, 2024 · 4 comments
Labels
5. scope: tracking Long-lived issue tracking long-term fixes or multiple sub-problems

Comments

@arunoruto
Copy link
Contributor

arunoruto commented Dec 23, 2024

Tracking description

While the support for CUDA is quite good on nixpkgs and ROCm is getting there, Intel's OneAPI is not entirely present. Like the tracking issue for ROCm, I wanted to have a list of packages contained in OneAPI's toolkits and track which are already packaged and still need to be.

Packages

  • Intel® oneAPI Level Zero (L0)
  • Intel® Video Processing Library (VPL)
  • Intel® CPU Runtime for OpenCL™ Applications with SYCL support - about aur
Base Toolkit
  • Intel® oneAPI DPC++/C++ Compiler
  • Intel® DPC++ Compatibility Tool
  • Intel® Distribution for GDB*
  • Intel® oneAPI DPC++ Library (oneDPL)
  • Intel® oneAPI Threading Building Blocks (oneTBB)
  • Intel® oneAPI Math Kernel Library (oneMKL)
  • Intel® oneAPI Deep Neural Network Library (oneDNN)
  • Intel® oneAPI Data Analytics Library (oneDAL)
  • Intel® oneAPI Collective Communications Library (oneCCL)
  • Intel® Integrated Performance Primitives
  • Intel® Cryptography Primitives Library
  • Intel® Advisor
  • Intel® VTune™ Profiler
HPC Toolkit
  • Base Toolkit
  • Intel® Fortran Compiler
  • Intel® MPI Library

Config

  • Like cudaSupport and rocmSupport, oneapiSupport could be provided to packages, which can have oneapi as an additional dependency, like pytorch, jaxlib, ...
  • OneAPI team?

Add a 👍 reaction to issues you find important.

@arunoruto arunoruto changed the title Tracking issue: OneAPI [Tracking] OneAPI Packages Dec 23, 2024
@pbsds pbsds added the 5. scope: tracking Long-lived issue tracking long-term fixes or multiple sub-problems label Dec 23, 2024
@aginiewicz
Copy link

Would love to see this happen. Will this include oneAPI runtime for CPU-only OpenCL? Looked at list of packages above, but cannot see one. Looking for something like this one – https://aur.archlinux.org/packages/intel-opencl-runtime – unless I'm not aware and this is already possible. What I looked at, is that intel-ocl works only on older CPUs (got Core Ultra, so no luck) and intel-compute-runtime only for GPUs (both integrated and discrete), and the CPU-only driver is distributed separately (https://www.intel.com/content/www/us/en/developer/articles/tool/opencl-drivers.html#cpu-section), but I cannot get it to show up on my machine.

@arunoruto
Copy link
Contributor Author

arunoruto commented Jan 22, 2025

Would love to see this happen. Will this include oneAPI runtime for CPU-only OpenCL? Looked at list of packages above, but cannot see one. Looking for something like this one – https://aur.archlinux.org/packages/intel-opencl-runtime – unless I'm not aware and this is already possible. What I looked at, is that intel-ocl works only on older CPUs (got Core Ultra, so no luck) and intel-compute-runtime only for GPUs (both integrated and discrete), and the CPU-only driver is distributed separately (https://www.intel.com/content/www/us/en/developer/articles/tool/opencl-drivers.html#cpu-section), but I cannot get it to show up on my machine.

While it isn't a part of a toolkit mentioned above, it falls under the "oneAPI" branding. It seems there is not shell option for the new opencl runtime, so .deb or .rpm packages need to be used. I found out the link for the newest deb package: https://apt.repos.intel.com/oneapi/pool/main/intel-oneapi-runtime-opencl-2025.0.4-1519_amd64.deb
But packaging a deb package needs some understanding of the underlying structure, which I am still trying to familiarize with! And example is the MKL package (and how it is packaged in Arch). This doesn't mean that the opencl runtime will be the same, but it can happen.
According to the AUR link you sent, it depends on the basetoolkit, which needs to be provided for the runtime to work! While the whole basekit is probably not needed, it does not specify which packages are needed tho...

But I can add it to the list above, and maybe it can be tackled in the future!

@aginiewicz
Copy link

Wonderful, thanks! Will be keeping an eye on this tracking issue then! While I was an Arch Trusted User in the past and packaged a lot of stuff there, I'm still exploring nix, so won't be of much help currently, though might come back later, when I get accustomed to nix packaging

@eclairevoyant
Copy link
Contributor

related: #74148

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
5. scope: tracking Long-lived issue tracking long-term fixes or multiple sub-problems
Projects
None yet
Development

No branches or pull requests

4 participants