3 ms·
Did this a few weeks ago as part of the ~annual check to see if we finally support non-linux local dev for graphistry folks. Super promising, some tweaks: - WS
by lmeyerov 5y ago
Did this a few weeks ago as part of the ~annual check to see if we finally support non-linux local dev for graphistry folks. Super promising, some tweaks:
- WSL2. Kernel virtualization feels as native as advertised, e.g., docker in wsl2/ubuntu is fast like docker in native ubuntu, vs. the slowness that is docker in os x
- Ubuntu 20.04 works, if I remember right
- We don't worry as much about library-level versions b/c we run via docker
- OpenCL does not work. There's some bits about intel & amd GPUs, but nada on nvidia
- Many nvidia-smi diagnostics do not work... and many ecosystem libraries assumed they did for stuff like initialization & memory management & monitoring. Prepare for whackamole of updating pydata etc. dependencies to ~December+
- TBD for GPU K8S; KinD/K3D seem likely via docker runtime passthrough, but minikube & friends seem riskier. Curious if anyone has that working in a non-painful setup, esp. w/ cross-container GPU sharing..
We still can't fully use+endorse WSL2 support for Nvidia hardware due to lack of even super minimal OpenCL versions, and risky core diagnostics surprises, but encouraging!
(Good time to shout: if you're curious about end-to-end client/server GPU computing and already active on opengl/webgl, we're looking for someone into helping the next 100X of our viz engine!)
- my123 5y ago> OpenCL does not work. There's some bits about intel [& amd] GPUs, but nada on nvidia This is planned to be fixed. WSL2’s GPU support currently doesn’t provide a path to provide an alternate OpenCL loader ICD location. (And not for OpenGL either) Microsoft is developing CLon12 at https://github.com/microsoft/OpenCLOn12 https://github.com/microsoft/OpenCLOn12 as the option to provide OpenCL out of the box.
- happycube 5y agoHuh... bit of a way off, but that could lead to a rather convoluted way to implement OpenCL on Vulkan (CLon12->DXVK)
- my123 5y agoD3D12 has more compute features than Vulkan has. It works out for DXVK because games often don’t use those, but it’ll cause much more issues with CLon12. By the way, if you are ready to have a _limited_ implementation without a full feature set because of Vulkan API limitations, clvk is a thing. The list of limitations of that approach is at https://github.com/google/clspv/blob/master/docs/OpenCLCOnVulkan.md https://github.com/google/clspv/blob/master/docs/OpenCLCOnVu... tldr: Vulkan and OpenCL SPIR-V dialects are different, and the former has significant limitations affecting this use case
- lmeyerov 5y agoEdit: Looks like OpenCL in WSL2 is still very much TBD -- https://github.com/microsoft/OpenCLOn12/issues/32 https://github.com/microsoft/OpenCLOn12/issues/32 --- Interesting, thanks: * OpenCL 1.2 -> DX12 coverage seems to be passing the repo's tests * Unclear what's left for either a manual build or an automatic/upstreamed mesa install (https://devblogs.microsoft.com/directx/directx-heart-linux/ https://devblogs.microsoft.com/directx/directx-heart-linux/). We saw the priority examples for the project during announce was ARM/mobile (2020), so still curious...