#oneapi — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #oneapi, aggregated by home.social.
-
Fanless AIM101 Edge System Integrates Intel Processor N150 and PCIe AI Accelerator Support
-
Even now, Thrust as a dependency is one of the main reason why we have a #CUDA backend, a #HIP / #ROCm backend and a pure #CPU backend in #GPUSPH, but not a #SYCL or #OneAPI backend (which would allow us to extend hardware support to #Intel GPUs). <https://doi.org/10.1002/cpe.8313>
This is also one of the reason why we implemented our own #BLAS routines when we introduced the semi-implicit integrator. A side-effect of this choice is that it allowed us to develop the improved #BiCGSTAB that I've had the opportunity to mention before <https://doi.org/10.1016/j.jcp.2022.111413>. Sometimes I do wonder if it would be appropriate to “excorporate” it into its own library for general use, since it's something that would benefit others. OTOH, this one was developed specifically for GPUSPH and it's tightly integrated with the rest of it (including its support for multi-GPU), and refactoring to turn it into a library like cuBLAS is
a. too much effort
b. probably not worth it.Again, following @eniko's original thread, it's really not that hard to roll your own, and probably less time consuming than trying to wrangle your way through an API that may or may not fit your needs.
6/
-
Even now, Thrust as a dependency is one of the main reason why we have a #CUDA backend, a #HIP / #ROCm backend and a pure #CPU backend in #GPUSPH, but not a #SYCL or #OneAPI backend (which would allow us to extend hardware support to #Intel GPUs). <https://doi.org/10.1002/cpe.8313>
This is also one of the reason why we implemented our own #BLAS routines when we introduced the semi-implicit integrator. A side-effect of this choice is that it allowed us to develop the improved #BiCGSTAB that I've had the opportunity to mention before <https://doi.org/10.1016/j.jcp.2022.111413>. Sometimes I do wonder if it would be appropriate to “excorporate” it into its own library for general use, since it's something that would benefit others. OTOH, this one was developed specifically for GPUSPH and it's tightly integrated with the rest of it (including its support for multi-GPU), and refactoring to turn it into a library like cuBLAS is
a. too much effort
b. probably not worth it.Again, following @eniko's original thread, it's really not that hard to roll your own, and probably less time consuming than trying to wrangle your way through an API that may or may not fit your needs.
6/
-
I'm getting the material ready for my upcoming #GPGPU course that starts on March. Even though I most probably won't get to it,I also checked my trivial #SYCL programs. Apparently the 2025.0 version of the #Intel #OneAPI #DPCPP runtime doesn't like any #OpenCL platform except Intel's own (I have two other platforms that support #SPIRV, so why aren't they showing up? From the documentation I can find online this should be sufficient, but apparently it's not …)
-
I'm getting the material ready for my upcoming #GPGPU course that starts on March. Even though I most probably won't get to it,I also checked my trivial #SYCL programs. Apparently the 2025.0 version of the #Intel #OneAPI #DPCPP runtime doesn't like any #OpenCL platform except Intel's own (I have two other platforms that support #SPIRV, so why aren't they showing up? From the documentation I can find online this should be sufficient, but apparently it's not …)
-
Just how deep is #Nvidia's #CUDA moat really?
Not as impenetrable as you might think, but still more than Intel or AMD would like
It's not enough just to build a competitive part: you also have to have #software that can harness all those #FLOPS — something Nvidia has spent the better part of two decades building with its CUDA runtime, while competing frameworks for low-level #GPU #programming are far less mature like AMD's #ROCm or Intel's #OneAPI.
https://www.theregister.com/2024/12/17/nvidia_cuda_moat/ #developers -
Just how deep is #Nvidia's #CUDA moat really?
Not as impenetrable as you might think, but still more than Intel or AMD would like
It's not enough just to build a competitive part: you also have to have #software that can harness all those #FLOPS — something Nvidia has spent the better part of two decades building with its CUDA runtime, while competing frameworks for low-level #GPU #programming are far less mature like AMD's #ROCm or Intel's #OneAPI.
https://www.theregister.com/2024/12/17/nvidia_cuda_moat/ #developers -
Howdy all - registrations are still open for the first oneAPI DevSummit hosted by the UXL Foundation! Learn about GPGPU programming, oneAPI and how companies are coalescing around #oneapi / #sycl
https://linuxfoundation.regfox.com/oneapiuxldevsummit2024Registration will closeat 5pm today. The DevSummit will start at 8pm PT or 8:30am IST. See you there!
-
📢 Introduction to #oneAPI, #SYCL2020 & #OpenMP offloading
📆September 23-25, 2024In this 3-day online course, HLRS - High-Performance Computing Center Stuttgart provides an introduction to Intel Corporation's oneAPI implementation 🖥
Read more & Register👉 https://www.hlrs.de/training/2024/intel-oneapi
-
Just one more day to submit your session for the UXL oneAPI DevSummit being held October 9th & 10th!
Learn more: https://sessionize.com/uxldevsummit
#SYCL #oneAPI #UXL -
Just one more day to submit your session for the UXL oneAPI DevSummit being held October 9th & 10th!
Learn more: https://sessionize.com/uxldevsummit
#SYCL #oneAPI #UXL -
-
A coalition led by Qualcomm, Google, and Intel, under the UXL Foundation, aims to break $2.2 trillion Nvidia's stronghold on the AI market by developing an open-source software suite that supports diverse AI accelerator chips, leveraging Intel's OneAPI. #nvidia #google #intel #Qualcomm #ai #opensource #chips #semiconductor #strategy #partnership #oneapi #api #engineer #engineering #software #market
-
A coalition led by Qualcomm, Google, and Intel, under the UXL Foundation, aims to break $2.2 trillion Nvidia's stronghold on the AI market by developing an open-source software suite that supports diverse AI accelerator chips, leveraging Intel's OneAPI. #nvidia #google #intel #Qualcomm #ai #opensource #chips #semiconductor #strategy #partnership #oneapi #api #engineer #engineering #software #market
-
Hey folks! We have two speaker slots available to talk about heterogeneous computing at our community led forum @ Berkeley - would someone be willing to speak in person at Berkeley? Please boost!#oneapi #sycl
https://www.meetup.com/oneapi-community-us/events/296111342/
Saturday Oct 7th
-
What an amazing talk by @airlied on the state of vendors, compute and community feedback. Please take the 45 minutes to watch - worth every minute! https://youtu.be/HzzLY5TdnZo
-
For those who have waited eagerly for the recording of our #oneapi meetup with @karolherbst - here it is! https://youtu.be/KUze0JbPSy8
#sycl #opencl #rustlang - if you are interested in joining our oneAPI meetup - feel free to subscribe here - https://www.meetup.com/oneapi-community-us/Next time we will be meeting with Stephano Cetola who will be talking about RISC-V, onAPI, and other things.
-
As an experiment, I created a fediverse magazine on kbin - https://kbin.social/m/oneapi_community
If you're interested in #oneapi - check it out. :)
-
Next week #oneAPI Meetup will feature @karolherbst - they'll be talking about rusticl, how openCL works in Mesa, and varriers to #SYCL and any other questions people want to entertain. :)
https://www.meetup.com/oneapi-community-us/events/294379731/?isFirstPublish=truePlease boost to those who might be interested ! :)
-
(Thread)
Wanted to give a quick thanks to @sri for having me on as part of the #OneAPI Accelerated compute panel yesterday
Had a good time discussing what does and doesn't work across oneAPI, #SYCL and how to deal with SYCL as a standard.
I also want to reiterate that SYCL or oneAPI as standards are not "magic bullets" for performance across all hardware
The major point of them, like most libraries and software stacks, is to get you to ~90% of performance without having to rewrite the stack
-
I'll be speaking during the OneAPI dev summit tomorrow, specifically the panel discussion on accelerated computing.
Partially as a meme/Sanity check the challenge of this afternoon:
Can I got from no installs to a GPU accelerated simulation of OpenFOAM using an Arc a770 on Linux?
Plan is #OpenFoam 2212, #petsc 3.19, #OneAPI 2023.1 and #mesa 23 (in case I need to fall back to #OpenCL)
-
Corporate #FLOSS at its worst: #NVIDIA controls the #Thrust library and its #CUDA, #OpenMP and #TBB backend. #AMD provides rocThrust, that is just Thrust with the CUDA part stripped an a new backend for #ROCm / #HIP. Nobody* is working on a backend for #SYCL
#Intel provides its own #oneAPI alternative as #oneDPL, which is NOT a drop-in replacement.This is why we can't have nice things.
*there's a dead project here
https://github.com/wdmapp/syclthrust -
Woot woot! Just found out that @vsoch just added me to the hpc.social blogs for #oneAPI and #sycl content! What a great way to start the new year - looking forward to reading all the other community related blogs. 🙂
Perhaps we can convince @illuhad and @Codeandrew to add their blogs ? 🙂
-
For community projects, ecosystems, or governance bodies, you might want to subscribe to the new community aggregated blog! For our newest members we welcome #oneapi and (previously on the other blog) #CaRCC! And we've placed our own tiny feed there too. https://hpc.social/community-blog/ ❤️
