CUDA Toolkit Release Notes • Hacker News Board

Re: CUDA Toolkit Release Notes

#31

Post by ActorNightly » Sun, Nov 24, 2019, 9:00 AM UTC

suyash wrote: post #22

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

I dont really understand this, why would you use a Mac for anything compute intensive?

Re: CUDA Toolkit Release Notes

#32

Post by xvilka » Sun, Nov 24, 2019, 9:03 AM UTC

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

Re: CUDA Toolkit Release Notes

#33

Post by zozbot234 » Sun, Nov 24, 2019, 9:04 AM UTC

suyash wrote: post #22

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

AIUI, Vulkan can be used for compute - so why not do that? It might work reasonably well on both nVidia and non-nVidia hardware. Of course, this requires GPU-enabled software to implement Vulkan support, but that's one-time work.

Re: CUDA Toolkit Release Notes

#34

Post by mikkelam » Sun, Nov 24, 2019, 9:08 AM UTC

ActorNightly wrote: post #31

suyash wrote: post #22

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

I dont really understand this, why would you use a Mac for anything compute intensive?

hackintosh

Re: CUDA Toolkit Release Notes

#35

Post by bayindirh » Sun, Nov 24, 2019, 9:16 AM UTC

mister_hn wrote: post #23

Fully understandable..anyways none is doing ML on Apple hardware due to ATi Chipsets.. last Apple HW with Nvidia graphic cards are old or running Linux or Windows with Bootcamp anyways

In my understanding, Radeon Instinct cards are not doing that bad. Yes, they're not supported by CUDA, but they're not slouching either.

Re: CUDA Toolkit Release Notes

#36

Post by llukas » Sun, Nov 24, 2019, 9:18 AM UTC

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.

You surely can write one yourself or pay for development. If that doesn't work maybe you could help developing one of the existing packages?

Re: CUDA Toolkit Release Notes

#37

Post by arvinsim » Sun, Nov 24, 2019, 9:29 AM UTC

snuxoll wrote: post #10

wlesieutre wrote: post #4

Not surprising given Apple’s apparent vendetta against Nvidia hardware

A well deserved vendetta, Nvidia has screwed Apple over multiple times going back to the PowerPC days. After the defective chipset fiasco one can’t blame them for cutting ties.

In the end, it's the customers who lose

Re: CUDA Toolkit Release Notes

#38

Post by mirekrusin » Sun, Nov 24, 2019, 9:35 AM UTC

pvg wrote: post #24

kragen wrote: post #20

Earlier quoted context omitted.

Apple hates hackers. Didn't the missing Esc key clue you in?

That only flies if Ctrl-[ also enables Nvidia support.

MacBooks with iPhone stripe don’t have Nvidia hardware.

Re: CUDA Toolkit Release Notes

#39

Post by pvg » Sun, Nov 24, 2019, 9:37 AM UTC

mirekrusin wrote: post #38

pvg wrote: post #24

Earlier quoted context omitted.

That only flies if Ctrl-[ also enables Nvidia support.

MacBooks with iPhone stripe don’t have Nvidia hardware.

The fair breeze blew, the white foam flew,

The furrow followed free

Re: CUDA Toolkit Release Notes

#40

Post by QuixoticQuibit » Sun, Nov 24, 2019, 9:44 AM UTC

snuxoll wrote: post #10

wlesieutre wrote: post #4

Not surprising given Apple’s apparent vendetta against Nvidia hardware

A well deserved vendetta, Nvidia has screwed Apple over multiple times going back to the PowerPC days. After the defective chipset fiasco one can’t blame them for cutting ties.

That seems like a very one-sided take considering Apple’s history.

Moreover, the reason is almost certainly related to Apple not wanting to proliferate Nvidia’s tools and instead force developers to use their Metal API. AFAIK Apple’s even abandoned OpenCL on macOS.