Developer Explains Why Explicit Sync Will Finally Solve the NVIDIA/Wayland Issues
Developer Explains Why Explicit Sync Will Finally Solve the NVIDIA/Wayland Issues
KDE developer Xaver Hugl explains why the explicit sync protocol will finally encourage the Wayland adoption among NVIDIA GPU users.
An article about Nvidia in the Linux community? Surely all the comments will be productive and discuss the topic at hand.
127Too little too late.
Already sold my 3070 and went for an 7900 XT bcs i got fed up with NVidia being lazy
80I had to update my laptop about two years ago and decided to go full AMD and it's been awesome. I've been running Wayland as a daily driver the whole time and and I don't even really notice it anymore.
14Even now, choosing between a free 4090 or a free 7900 XTX would be easy.
9It totally depends on your usecase.
NVidia runs 100% rocksolid on X11.
If you're someone who reallse uses CUDA and all their stuff and don't care about Wayland. NVidia is the choice you have to make. Simple as that.
If you don't care about those things or are willing to sacrifice time and tinker around with AMDs subpar alternatives, AMD is the way to go.
Because let's face it. AMD didn't care about machine learning stuff and they only now begin to dabble in it. They lost a huge amount of people who work with those things as their day job. They can't tell their bosses and/or clients that they can't work for a week or two until they figured out how to get this alternative running that is just starting to care about that field of work.
10
If the day comes I want to upgrade my 3080 I’ll switch to an AMD solution but until then I’ll take any improvement I can get from Nvidia.
7I don't believe Nvidia were the one's being lazy in this regard, they submitted the merge request for explicit sync quite some time ago now. Wayland devs essentially took their sweet time merging the code.
-3
Explicit Sync sounds like some kind of porn syncing program.
36That's why it's better.
7It's like Apple syncs videos with explicit lyrics in Apple Music when you play a song.
4and now Nvidia users can use it on wayland! 🦀
1
I will never buy anything with Nvidia again.
28Unfortunately, those of us doing scientific compute don't have a real alternative.
ROCm just isn't as widely supported as CUDA, and neither is Vulkan for GPGPU use cases.
AMD dropped the ball on GPGPU, and Nvidia is eating their lunch. Linux desktop users be damned.
46yep 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.
10I find it eerly odd how amd seems to almost intetionally stay out nvidia’s way in terms of cuda and couple other things. I dont wish to speculate but considering how ai is having a blowout yet AMD is basically not even trying, it feels as if the nvidia ceo beying cousins with amd’s ceo has something to do with it. Maybe i am reading too much into it but there’s something going on. Why would amd leave so much money on the table?
4
hey look, the yearly "nvidia is finally fixing wayland support" post!
25Now all they need is a complete nvidia-settings application under Wayland that allows for coolbits to be set, and I may be able to use Wayland. For some reason, my RTX 2070S boosts far higher than the already overclocked from factory boost clocks, resulting in random crashing - I have to use GWE to limit boost clocks to OEM specs to prevent crashing.
Strangely enough, this was never a problem under Windows.
10Will this make my terminal faster?
9It will not though. Explicit sync is not a magic solution, it's just another way of syncing GPU work. Unlike implicit sync it needs to be implemented by every part of the graphical stack. Just because Nvidia is implementing it will not solve issues with compositors not having it, and graphical libraries not having it, and apps not supporting it, and so on and so forth. It's a step in the right direction but it won't fix everything overnight like some people think.
Also it's silly that this piece mentions Wayland and Nvidia because (1) Wayland doesn't implement sync of any kind, they probably meant to say "the Wayland stack" and (2) Nvidia is not the only driver that needs to implement explicit sync.
3will not solve issues with compositors not having it
Many compositors already have patches for explicit sync which should get merged fairly quickly.
graphical libraries not having it
Both Vulkan and OpenGL have support for explicit sync
apps not supporting it
Apps don't need to support it, they just need to use Vulkan and OpenGL, and they will handle it.
Wayland doesn't implement sync of any kind, they probably meant to say "the Wayland stack"
Wayland has a protocol specifically for explicit sync, it's as much a part of Wayland as pretty much anything else that's part of Wayland.
Nvidia is not the only driver that needs to implement explicit sync.
Mesa has already merged explicit sync support.
67so basically every single statement was incorrect ? lol
23
Doesn't this mean application developers will have to explicitly sync the graphical state? If that's the case, then devs will have to write custom code for it to work on NVIDIA, correct? If so, I doubt this will "finally solve" any issues, only finally provide the ability to solve them... explicitly and with a lot of dev work + required awareness.
How come AMD doesn't need this?
P.S Obligatory Fuck NVIDIA
Anti Commercial AI thingy
CC BY-NC-SA 4.0 :::___
-10Nah, explicit sync is the objectively better model if you want high performance. Android went for explicit sync right from the start and from what I gather also Intel and AMD prefer it. The problem is, that the graphics stacks on Linux have been using implicit sync for ages and so far no one dared to change the status quo. Nvidia was "simply" rejecting implementing an inferior mechanism in their driver. While somewhat understandable, it was still a decision on the back of their users.
5Permanently Deleted
2