5 ms·
IIRC, they were primarily interested in getting GPU acceleration (for ML tasks) to work in WSL2. I presume getting GUI working on top of those GPU APIs was a t
by gigel82 5y ago
IIRC, they were primarily interested in getting GPU acceleration (for ML tasks) to work in WSL2.
I presume getting GUI working on top of those GPU APIs was a trivial task (and maybe done by one of their interns or during a hackathon).
- reilly3000 5y agoThat sounds like the killer app. GPU passthru can be an absolutely gnarly undertaking with any virtualization system.
- gobookdev 5y agoAnyone could already do it with a few lines of code. Edit: Seems people don't believe me, here's an article how to do it: https://techcommunity.microsoft.com/t5/windows-dev-appconsult/running-wsl-gui-apps-on-windows-10/ba-p/1493242 https://techcommunity.microsoft.com/t5/windows-dev-appconsul...
- rrss 5y agoThat shows how to set up an X server in windows that WSL can access. How do you get GPU acceleration for ML tasks using X11?
- PufPufPuf 5y agoGPU passthrough on WSL2 is a thing since around December 2020 -- but I'm not sure if it's in stable yet, I had to install an insider build for it. It works surprisingly well and I was able to develop my ML project using it (with the help of VSCode devcontainers)
- jimmaswell 5y agoWhy did you want to develop it through WSL2 instead of just compiling it on windows?
- mook 5y agoIt sounds like they did significant work getting the whole stack to work well, from Wayland to the RDP back-end to improvements to the RDP client on the Win32 side. Your interns must be rock stars on meth.
- kafkaIncarnate 5y agoMost likely energy drinks + Adderall + financial insecurity. Adderall, Meth, same thing.