Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Is that not the case?

it is - they're laughably slow and not even supported by latest CUDA

> NVIDIA Driver support for Kepler is removed beginning with R495. CUDA Toolkit development support for Kepler continues through CUDA 11.x.



But Deepseek R1 doesn't use CUDA, so maybe for this specific case, it isn't a big deal?


> it isn't a big deal?

friend you shouldn't make comments like this unless you understand the definitions of the words. Deepseek wrote some parts of their kernels using PTX. newsflash: PTX support for features is lockstep with CUDA support for the same features ie the fact that CUDA doesn't support it means you couldn't write the PTX to use those features either.


It is poor form to condemn someone from asking a question.

Thank you for providing the information to clear up ignorance though.


this is a question:

> is deepseak's use of PTX instead of CUDA relevant here?

this is a conclusion/assumption thinly veiled as a question

> Deepseek R1 doesn't use CUDA, so ... it isn't a big deal?

note, genuine questions don't already presuppose an answer.


Asking if it is a big deal or not is definitely a question ;) Thank you for providing the information I was missing though.


The PTX hack is for backend runner and training infra, the public weights are often executed using existing backends. Especially R1-distill-* models are.


the two things (weights and kernels) have nothing to do with each other in the slightest. again i wish people would take a beat before commenting out of their depth and consider whether their comment adds to the conversation or not.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: