News for hackers. Stuff that matters.

A comment on Nvidia’s New Policy Limits GeForce Data Center Usage.

Re:Nvidia’s New Policy Limits GeForce Data Center Usage by sabalaba on Thursday December 21, 2017 @11:33PM (#15985295)
Developers should be mad about this. Here's where to start contributing to open alternatives:

ROCm: https://rocm.github.io/

OpenCL: https://www.khronos.org/opencl/

TensorFlow: https://github.com/tensorflow/tensorflow

Nouveau: https://nouveau.freedesktop.org/wiki/

[ Parent | on HN ]
Re:Nvidia’s New Policy Limits GeForce Data Center Usage by reilly3000 on Friday December 22, 2017 @02:13AM (#15985779)
TensorFlow depends exclusively (st time of writing) on CUDA for GPU acceleration. Leaning on them to support OpenCL fully would unlock the world of AMD GPUs that are move affordable and don’t have the same crazy EULA. I regret having bought GeForce cards for machine learning now...
[ Parent | on HN ]
Re:Nvidia’s New Policy Limits GeForce Data Center Usage by arcanus on Friday December 22, 2017 @11:00AM (#15988364)
Actually, AMD has a version of tensorflow that works on their devices:

https://github.com/ROCmSoftwarePlatform/hiptensorflow

[ Parent | on HN ]
Re:Nvidia’s New Policy Limits GeForce Data Center Usage by larrykwg on Friday December 22, 2017 @05:26AM (#15986463)
TensorFlow also supports Intel Xeon Phi as an alternative

https://software.intel.com/en-us/articles/tensorflow-optimiz...

[ Parent | on HN ]
Re:Nvidia’s New Policy Limits GeForce Data Center Usage by make3 on Sunday December 24, 2017 @10:16PM (#16002451)
afaik Xeon phi doesn't come close to the performance per buck of gpus in deep learning
[ Parent | on HN ]
Re:Nvidia’s New Policy Limits GeForce Data Center Usage by matt4077 on Friday December 22, 2017 @03:59AM (#15986159)
Instead of “leaning on them”, you can submit patches. The OpenCL effort is well underway, and pull requests are accepted every day.
[ Parent | on HN ]
Re:Nvidia’s New Policy Limits GeForce Data Center Usage by fauigerzigerk on Friday December 22, 2017 @06:23AM (#15986711)
>Instead of “leaning on them”, you can submit patches

Do yo know that he has the right skill set or the time to maintain the code for years to come? Do you know that the effort would be economically viable for him like it could be for AMD or perhaps Google?

If not then I would prefer if he didn't submit a patch, because he would be wasting everyone's time.

Sometimes the best contribution you can make to an open source project is to express your interest in particular features so that those who really can submit a patch know that there is demand for it.

[ Parent | on HN ]