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

CUDA Toolkit Release Notes

docs.nvidia.com

Post reply on HN
Print view View original

81–90 of 126 posts

Re: CUDA Toolkit Release Notes

#81

Post by dahart »

andybak wrote: post #54
pvg wrote: post #53

Earlier quoted context omitted.

As the whiner who whined about this title - the story isn't worthy of note at all, other than someone fishing a supposedly-important detail out of it and putting it in the title. Apple hasn't as much as sold a machine with an Nvidia GPU for many years. This non-editorializing thing is explained in great illustrative detail here: https://news.ycombinator.com/item?id=21617907

1. I didn't know the fact highlighted in the original title 2. Doesn't this have an impact on eGPUs, Hackintoshes and other customizations? It basically means heavy GPU-based work is pretty much a Linux/Windows only thing now. Huge problem as machine learning starts to become an interest topic for people in the art and design community.

> Huge problem as machine learning starts to become an interest topic for people in the art and design community.

Out of curiosity, what Mac apps are you and other professionals using for art & design? Being a part time artist & ex-Mac person, I thought the stereotype of Mac being an artist/designer’s machine was almost gone. Most professional artists I know have had to switch away from Mac. To be fair, most artists I know are doing 3d and need GPUs. But I’m honestly wondering what else is keeping people on Mac and how well the platform is serving professional designers and artists today.

Re: CUDA Toolkit Release Notes

#82

Post by dahart »

sorenjan wrote: post #69
suyash wrote: post #22

We need a CUDA alternative for non NVIDIA gpu's, specially on a Mac.

I recently looked into GPGPU programming, and it seems to be a bit of a mess, which is surprising seeing how long it's been around and how much it is used. I think a large part of it is due to Nvidia using their strong position to hamper anything other than Cuda. OpenCL 2.0 was announced in 2013, Nvidia added OpenCL 2.0 "for evaluation purposes" in 2017. I don't think they have final support yet. OpenCL 2.1 uses the…

> I don't want to use a proprietary language

CUDA is mostly just limited C++. A couple of the interesting points in the release notes: “Added support for CUDA Virtual Memory Management APIs.; 10.2 now includes libcu++, a parallel standard C++ library for GPUs.” Those things make CUDA even easier to treat like regular C++.

The language isn’t really the force keeping people in or out, the libraries & tools are. cuDNN, for example, is something you can’t get in OpenCL.

Re: CUDA Toolkit Release Notes

#84

Post by ktm5j »

amelius wrote: post #83

I'm using CUDA under Ubuntu, and have noticed that the CUDA library uninstalls itself every so often. Has anyone else experienced this?

You probably installed a kernel update and the nvidia kernel module didn't recompile itself. You can avoid having to reinstall the whole driver package by just running "dkms autoinstall" and then "modprobe nvidia"

You may first need to unload any loaded nvidia modules (built for an older kernel).. So some combination of "rmmod nvidia_modeset" "rmmod nvidia_uvm" "rmmod nvidia_drm" "rmmod nvidia" and then run dkms

I run a ~1000 node server room for a computer science graduate program at a university.. keeping these drivers built and loaded properly has been a nightmare! Nvidia really needs to get things worked out if they want to keep pushing the GPGPU stuff

Re: CUDA Toolkit Release Notes

#85

Post by whywhywhywhy »

xvilka wrote: post #32

This is why CUDA and NVIDIA are a cancer. Such an important piece of infrastructure for both graphics and ML should be open source.

It works fine on Windows and Linux. Apple didn't even ship a computer with a replaceable GPU for 6 years.

Nvidia spent money building the superior SDK and that's why CUDA is an important piece of infrastructure. Apple half heatedly supported OpenCL, then killed it, then pushed Metal and all this time didn't ship a computer that could even take advantage of this power.

Closed tech is bad but Apple killed off the only real open competitor and replaced it with something even more closed.

Re: CUDA Toolkit Release Notes

#86

Post by lol768 »

archi42 wrote: post #80
dang wrote: post #19

Submitted title was "Nvidia drops support for CUDA on macOS". We changed that for a while to "CUDA 10.2 is the last release to support macOS", which is language from the article itself. Since then someone emailed and asked why the title was like that in light of the discussion at https://news.ycombinator.com/item?id=21617016 , so I've reverted to the article's title. Edit: If the article were more a burying the lede…

Personal opinion: I really don't care about "CUDA Toolkit Release Notes" or probably most other "$stuff Release Notes" on HN. I only opened the comments because others here seemed to upvote it more than I anticipated and thought "there must be something special about this release" - and indeed, nVidia dropping MacOS support is something that's worth knowing (even as a Linux dev). Thus I personally would like to eithe…

> Personal opinion: I really don't care about "CUDA Toolkit Release Notes" or probably most other "$stuff Release Notes" on HN. I only opened the comments because others here seemed to upvote it more than I anticipated and thought "there must be something special about this release" - and indeed, nVidia dropping MacOS support is something that's worth knowing (even as a Linux dev).

Would have to agree here, too. Part of the problem is that there's no obvious indicator to show that the title has changed (some sort of "post title history" feature would be useful here) which then leaves you (as a latecomer to the article) confused as to what's remarkable about something which would normally perhaps be considered mundane, and confused as to the context against most previous comments were made.

Re: CUDA Toolkit Release Notes

#87

Post by rrss »

sorenjan wrote: post #69
suyash wrote: post #22

We need a CUDA alternative for non NVIDIA gpu's, specially on a Mac.

I recently looked into GPGPU programming, and it seems to be a bit of a mess, which is surprising seeing how long it's been around and how much it is used. I think a large part of it is due to Nvidia using their strong position to hamper anything other than Cuda. OpenCL 2.0 was announced in 2013, Nvidia added OpenCL 2.0 "for evaluation purposes" in 2017. I don't think they have final support yet. OpenCL 2.1 uses the…

Who actually supports opencl 2.0? ROCM, which AFAICT is AMD's new preferred platform, only supports opencl 1.2 also.

Re: CUDA Toolkit Release Notes

#88

Post by dahart »

jsgo wrote: post #73
pvg wrote: post #53

Earlier quoted context omitted.

As the whiner who whined about this title - the story isn't worthy of note at all, other than someone fishing a supposedly-important detail out of it and putting it in the title. Apple hasn't as much as sold a machine with an Nvidia GPU for many years. This non-editorializing thing is explained in great illustrative detail here: https://news.ycombinator.com/item?id=21617907

Perhaps they haven’t sold Nvidia hardware, but the allowance of Nvidia’s web drivers so that I could connect my eGPU w/ GTX 1080 to the 13in Macbook Pro was one of the primary reasons I bought the MBP. It is fine if they want to kill off features off upcoming hardware, but killing off the capacity to use something that was used for months is not the best look. If Metal Only was the goal, add a prompt when someone ena…

Yep; you’re right. And Metal isn’t the only goal. Preventing people from going off the reservation is the goal. I can see both sides; there are both upsides and downsides for both Apple and their customers. Either way, at this point, Apple’s strategy is clear and widely known. It sucks you can’t use eGPU with Mac, and I’d still be primarily using a Mac if you could, but it’s no longer an available choice. As consumers, the only option now is to vote with our pocketbooks.

Re: CUDA Toolkit Release Notes

#89

Post by fortran77 »

mlazos wrote: post #18
alphagrep12345 wrote: post #11

Why doesn't apple support NVIDIA though? Considering the whole ML and AI community use only NVIDIA GPUs, it sucks that we can't use apple laptops for the same.

I think for the larger models now it's more likely people are remotely logging into GPU clusters at this point. I don't think it will be that big of a change.

I do GPGPU programming for a livng. It's all NVIDIA. They have the best developer support and the best hardware.

It's nice having a laptop with nvidia so I can test and develop software even if real models are run on big iron.

Re: CUDA Toolkit Release Notes

#90

Post by vkaku »

pilooch wrote: post #51
andybak wrote: post #43

Earlier quoted context omitted.

Any title that gives us a clue why the story is worthy of note. At the moment it's frustrating as you have to click through to find out if you want to click through. (title at the time of my comment was "CUDA Toolkit Release Notes")

As an ML + open source developer for over 10y, MacOS support for deep learning is already long gone, Linux is the prime AI/ML OS. However, Apple and NVidia parting away is a good omen for GPU competition I believe. Whatever Apple hw comes up with, if usable outside MacOS software stack, it'd be an interesting alternative.

Emphasis on `if usable`

I don't think the general crowd will adapt itself to go on to Apple's stack unless it is radically better.

Till Apple gets its developers to use what it makes, by enforcing it on its App Store, like the way it pushed people for Webkit - Otherwise it won't have takers.

Post reply on HN