bolha.us

0 posts0 participants0 posts today

AmartyaMy brain is absolutely fried. Today is the last day of coursework submissions for this semester. What a hectic month. DNN with PyTorch, Brain model parallelisation with MPI, SYCL and OpenMP offloading of percolation models,hand optimizing serial codes for performance. Two submissions due today. Submitted one and finalising my report for the second one. Definitely having a pint after this<a href="https://fosstodon.org/tags/sycl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sycl</a> <a href="https://fosstodon.org/tags/hpc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hpc</a> <a href="https://fosstodon.org/tags/msc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#msc</a> <a href="https://fosstodon.org/tags/epcc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#epcc</a> <a href="https://fosstodon.org/tags/cuda" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cuda</a> <a href="https://fosstodon.org/tags/pytorch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pytorch</a> <a href="https://fosstodon.org/tags/mpi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mpi</a> <a href="https://fosstodon.org/tags/openmp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openmp</a> <a href="https://fosstodon.org/tags/hectic" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hectic</a> <a href="https://fosstodon.org/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#programming</a> <a href="https://fosstodon.org/tags/parallelprogramming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#parallelprogramming</a> <a href="https://fosstodon.org/tags/latex" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#latex</a>

pafurijazIt seems that <a href="https://mastodon.social/tags/Vulkan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Vulkan</a> could be the real alternative for using <a href="https://mastodon.social/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AI</a> on GPUs or CPUs of any brand, without necessarily having to rely on <a href="https://mastodon.social/tags/CUDA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CUDA</a> or <a href="https://mastodon.social/tags/AMD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AMD</a>'s <a href="https://mastodon.social/tags/ROCm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ROCm</a>. I thought <a href="https://mastodon.social/tags/SYCL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SYCL</a> was the alternative. This might finally free us from of monopoly <a href="https://mastodon.social/tags/Nvidia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nvidia</a>. <a href="https://mastodon.social/tags/Khronos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Khronos</a>

Giuseppe BilottaIt's out, if anyone is curious <a href="https://doi.org/10.1002/cpe.8313" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://doi.org/10.1002/cpe.8313</a>This is a “how to” guide. <a href="https://fediscience.org/tags/GPUSPH" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPUSPH</a>, as the name suggests, was designed from the ground up to run on <a href="https://fediscience.org/tags/GPU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPU</a> (w/ <a href="https://fediscience.org/tags/CUDA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CUDA</a>, for historical reasons). We wrote a CPU version a long time ago for a publication that required a comparison, but it was never maintained. In 2021, I finally took the plunge, and taking inspiration from <a href="https://fediscience.org/tags/SYCL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SYCL</a>, adapted the device code in functor form, so that it could be “trivially” compiled for CPU as well.<a href="https://fediscience.org/tags/HPC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HPC</a> <a href="https://fediscience.org/tags/GPGPU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPGPU</a>

Brett Edmond CarlockDo I have anyone in my wider network with skills in programming CUDA, SYCL, and OpenCL?We want to determine feasibility of migrating CUDA-only code to SYCL (via SYCLomatic?): OpenCV feature detection/extraction modules (SIFT, HAGOG, ORB, AKAZE).The intent is to upstream all feasible work. This, hopefully, should stand to benefit everyone instead of being limited to NVIDIA.Currently in info gathering/people connecting phase, not yet funded & ready to go.<a href="https://mastodon.online/tags/CUDA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CUDA</a> <a href="https://mastodon.online/tags/SYCL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SYCL</a> <a href="https://mastodon.online/tags/OpenCL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenCL</a> <a href="https://mastodon.online/tags/OpenCV" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenCV</a>

FCLCTime for an <a href="https://mast.hpc.social/tags/introduction" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#introduction</a>! I'm a young Canuck with interests/experience in <a href="https://mast.hpc.social/tags/HPC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HPC</a>, <a href="https://mast.hpc.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a>, <a href="https://mast.hpc.social/tags/BLAS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BLAS</a>, <a href="https://mast.hpc.social/tags/SYCL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SYCL</a>, <a href="https://mast.hpc.social/tags/C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#C</a>, <a href="https://mast.hpc.social/tags/AVX512" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AVX512</a>, <a href="https://mast.hpc.social/tags/Rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Rust</a>, heterogeneous compute & other such things. Currently my personal projects are bringing <a href="https://mast.hpc.social/tags/FP16" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FP16</a> to the <a href="https://mast.hpc.social/tags/OpenBLAS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenBLAS</a> library, working to standardize what Complex domain BLAS FP16 kernels/implementations should look like, and making sure <a href="https://mast.hpc.social/tags/SYCL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SYCL</a> is available everywhere. I also write every now and again. Here's the tail of AVX512 FP16 on Alderlake <a href="https://gist.github.com/FCLC/56e4b3f4a4d98cfd274d1430fabb9458" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://gist.github.com/FCLC/56e4b3f4a4d98cfd274d1430fabb9458</a>

Recent searches

Search options

Administered by:

Server stats:

#sycl