196
Developer Explains Why Explicit Sync Will Finally Solve the NVIDIA/Wayland Issues (9to5linux.com)
submitted 2 years ago by to c/linux@lemmy.ml
41 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 10 points 2 years ago (1 child)

yep yep and yep.

and they've been eating their lunch so long at this point I've given up on that changing.

The new world stands in cuda and that's just the way it is. I don't really want an nVidia, radeon seems far better for price to performance . Except I can justify an nVidia for work.

I can't justify a radeon for work.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 11 points 2 years ago (2 children)

    Long term, I expect Vulkan to be the replacement to CUDA. ROCm isn't going anywhere...

    We just need fundamental Vulkan libraries to be developed that can replace the CUDA equivalents.

    • cuFFT -> vkFFT (this definitely exists)
    • cuBLAS -> vkBLAS (is anyone working on this?)
    • cuDNN -> vkDNN (this definitely doesn't exist)

    At that point, adding Vulkan support to XLA (Jax and TensorFlow) or ATen (PyTorch) wouldn't be that difficult.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 18 points 2 years ago

    wouldn't be that difficult.

    The amount of times I said that only to be quickly proven wrong by the fundamental forces of existence is the reason that's going to be written on my tombstone.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 3 points 2 years ago (1 child)

    I think. it's just path stickiness at this point. CUDA works and then you can ignore it's existence and do the thing you actually care about. ML in the pre CUDA days was painful. CUDA makes it not painful. Asking people to return to painfully..

    Good luck..

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •