Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

CUDA on Windows Subsystem for Linux 2

devblogs.nvidia.com

Post reply on HN
Print view View original

191–200 of 221 posts

Re: CUDA on Windows Subsystem for Linux 2

#191

Post by noir_lord »

calaphos wrote: post #186
noir_lord wrote: post #181

Earlier quoted context omitted.

> (aka the Wayland Nightmare and DPI issues everywhere) The picture is more mixed than you present. I use Fedora at 2560x1440@14" and 2 by 3840x2160@27 and the dpi thing isn't an issue, set your font scaling to 1.5 and that's about all you need to do. I dual boot windows and fedora (for gaming in the former and dev in the latter) and Windows 10 is by far more unpleasant to deal with, updates that tie your machine up…

In my experience high DPI actually works somewhat decently and those fractional stuff can be fixed with don't scaling. At least if you only use one monitor. I personally have two I would use with 1.25x and no scaling which is just not possible with the x11 model. Additionally having two monitors completely breaks vsync with very ugly tearing lines. And Wayland on Nvidia has been very unsuccessful for me. Even when I…

In Firefox you can force hardware acceleration in about config which resolves tearing for me on scroll, it's off by default for conservative reasons.

Re: CUDA on Windows Subsystem for Linux 2

#192

Post by read_if_gay_ »

jentist_retol wrote: post #153
mattip wrote: post #149

I have the opposite setup: Linux is my primary os and I have windows on a separate ssd that I can either dual boot into or use in qemu from Linux. It gets used once a month or so. I don’t game, so maybe I am the wrong demographic, but I don’t miss anything from windows. All my document work (even right-to-left languages) works well on Linux, default Ubuntu gnome. I use two monitors, with different resolution. What am…

Last time I tried it, I installed Ubuntu 18.04LTS, updated, installed the recommended graphics driver, and then the machine would not boot after that. I recently tried 20.04LTS on a laptop, with an external GPU over tb3 - it works! However, I really struggled to rectify the display density of my external 4k with the laptop's built in 1080p. I had other show stopper bugs, besides bad scaling, however. :( What you're m…

> What you're missing is the ability to open a game for a quick session while keeping your work open in the background.

Absolutely possible with Wine or QEMU.

> What you're missing is that desktop linux is famously unpolished, and worse, brittle

Correct, but arguably also true for Windows. There’s no Linux distro that has had two settings panels for years. IMO the only polished OS is macOS.

Re: CUDA on Windows Subsystem for Linux 2

#193

Post by patrec »

fulafel wrote: post #159
patrec wrote: post #65

Earlier quoted context omitted.

> I personally don't get why any developer would prefer Windows over Linux Because windows now literally has all the stuff Linux has plus a lot more. The only reason for a well paid developer to prefer linux over windows for a desktop OS is that you don't need any of the extra stuff (a decent desktop experience, hardware support and a commercial end user software eco system) or that you have some fundamental objectio…

> The only reason for a well paid developer to prefer linux that you don't need any of the extra stuff (a decent desktop experience, [...list of several more "linux sucks" opinions]) I think you'll find many Linux devs who have previously used or considered Windows have their own list of "windows sucks" reasons. (By "Well paid", are you referring to people who are willing to spend money on big ticket desktop sw, or p…

I simply meant that price can be another valid reason to prefer linux on the desktop, but not one that applies to most of the HN readership.

Re: CUDA on Windows Subsystem for Linux 2

#194

Post by fluffything »

jchw wrote: post #87
anaisbetts wrote: post #21

Having set this up, this is going to be absolutely huge for ML. A lot of nonsense is getting cut down by this: 1. You don't have to install special CUDA-specific drivers that are behind the normal gaming drivers anymore. You'll soon be able to just use the Regular nVidia Drivers (and even now, all you need to do is install a Beta driver version). That's huge for someone just starting out, they don't have to have "the…

> (aka the Wayland Nightmare and DPI issues everywhere) It’s more of a pick-one. Wayland has pretty good per monitor scaling; your X11 apps will be blurry but that’s about all I’ve experienced. The Windows DPI nightmare long surpassed it anyways. On a typical Wayland desktop the usual biggest problem is the DPI being set wrong for a monitor. Even on X11 the worst you get is applications that don’t scale correctly. On…

> Meanwhile Linux with Wayland has progressed meaningfully and is still being regarded with unwarranted disdain nonetheless.

That's because things don't work.

I moved from i3 to Sway and back to i3 because Sway didn't deliver of being compatible with i3.

Then there is the xdg portal mess which makes screen sharing through a web browser weird.

And also the whole XForawarding mess, which makes all Apps using it blurry in HiDPI. I use my computer for work, and 99% of it happens in emacs. The remaining 1% is using Chromium, which also does not support Wayland yet, so for me 100% of my wayland experience on HiDPI amounts to "all text on Wayland is blurry". There is no "HiDPI per-App" setting to fix this, scaling to 1.5x is also bad, etc. And that's without entering on the "wl-roots will never support nvidia thing". I need to use both AMD and nvidia hardware for work. I don't care about whether Wayland's desktop war (e.g. Sway) against nvidia, who has 50% of the GFX market, and 99% of the compute market, is honorable or not. But I do care about not being able to work on Wayland while X works just fine.

Sway devs say that this is 100% nvidias fault. From my POV, all other desktops manage to work with nvidia's hardware just fine, Sway does not, so I see this as being 100% Sway's fault. Without an i3 replacement I can't use Wayland, so until this fanaticism finished, I'll probably won't be able to use it.

Re: CUDA on Windows Subsystem for Linux 2

#195

Post by deno »

0xFFC wrote: post #94
deno wrote: post #51

Earlier quoted context omitted.

It’s not GPU pass-through, it’s paravirtualization.

Can you explain about paravirtualization?

The name “paravirtualization” is sort of misleading. It has more to do with history of virtualization than anything to do with technical aspects of it. The intention was to separate it from full on emulation, which is much slower. All modern virtualization is paravirtualization, unless you’re trying to emulate something specifically, e.g. develop for an ARM µc on an x64 workstation.

Technically it just means there’s a client & server components and they communicate through some IPC. In this example you’re talking to a GPU driver running on the host, instead of the GPU directly. The communication goes through a VM boundary, the host driver accesses the device, then returns the result through the boundary, once more. You could just as well do all of this via a network socket, it would just be a little slow.

When you “pass-through” a device the guest is talking to it directly, all the host has to do is set up the IOMMU to limit the guest and the device from accessing the host’s or other guests’ memory. Basically VLANs for PCIe and the IOMMU is a firewall.

Re: CUDA on Windows Subsystem for Linux 2

#196

Post by bzb3 »

SXX wrote: post #182
bzb3 wrote: post #114

Earlier quoted context omitted.

It's incredible that people like you are bitter because others are given a choice and they don't choose what you would want them to. And all in the name of freedom, no less.

I have no bitterness here, just facts. It's important to understand that none of these WSL features has anything to do with open source. It's exactly your standard "extend" stage. See: proprietary hypervisor runs OS with a patched non-upstreamable Linux kernel and then there is proprietary userspace drivers and libraries that able to talk to their proprietary parts inside Windows. Can any of it be used with different…

Of course it could, it's an open API. Others could use it if they wanted to.

Re: CUDA on Windows Subsystem for Linux 2

#198

Post by jen20 »

alwaysanon wrote: post #171
jen20 wrote: post #74

Earlier quoted context omitted.

I tried Windows 10 Pro and Windows 2019 Server about 2 months ago on a self-built computer (my first in ~15 years). What I found was: - driver support was atrocious for Windows server, and also for Windows 10. Almost every component from a fairly standard Ryzen build installed some form of custom skinned crapware to get basic functionality - spyware and advertising was everywhere. - the UI is a mess of old and new. I…

On the spyware part it can be all turned off. They give the Group Policy tools to do it to 'Enterprise Customers' but it is all there in the settings/registry and tools like this will flip it all off for you quickly and easily. https://www.oo-software.com/en/shutup10

Giving the ability to “opt-out” of spyware does not make it OK. I’m bored of hearing that tired excuse for poor behaviour.

Re: CUDA on Windows Subsystem for Linux 2

#199

Post by SXX »

bzb3 wrote: post #196
SXX wrote: post #182

Earlier quoted context omitted.

I have no bitterness here, just facts. It's important to understand that none of these WSL features has anything to do with open source. It's exactly your standard "extend" stage. See: proprietary hypervisor runs OS with a patched non-upstreamable Linux kernel and then there is proprietary userspace drivers and libraries that able to talk to their proprietary parts inside Windows. Can any of it be used with different…

Of course it could, it's an open API. Others could use it if they wanted to.

If Microsoft or Nvidia wanted to use open APIs they would just support technologies that already exist, e.g there is GPU virtualization with Virgil 3D. There also VirtIO which is standard for all kind of virtualized interfaces, but again Microsoft only interested in using their proprietary tech.

Microsoft could also just use Vulkan instead of bringing proprietary Direct3D user pace to Linux. Or might be they could actually open source parts of their stack, but then it's will be against their vendor lock-in.

Re: CUDA on Windows Subsystem for Linux 2

#200

Post by SomeoneFromCA »

calaphos wrote: post #186
noir_lord wrote: post #181

Earlier quoted context omitted.

> (aka the Wayland Nightmare and DPI issues everywhere) The picture is more mixed than you present. I use Fedora at 2560x1440@14" and 2 by 3840x2160@27 and the dpi thing isn't an issue, set your font scaling to 1.5 and that's about all you need to do. I dual boot windows and fedora (for gaming in the former and dev in the latter) and Windows 10 is by far more unpleasant to deal with, updates that tie your machine up…

In my experience high DPI actually works somewhat decently and those fractional stuff can be fixed with don't scaling. At least if you only use one monitor. I personally have two I would use with 1.25x and no scaling which is just not possible with the x11 model. Additionally having two monitors completely breaks vsync with very ugly tearing lines. And Wayland on Nvidia has been very unsuccessful for me. Even when I…

Never had tearing issues on dual display Linux setup (currently using one, no tearing).
Post reply on HN