129
Linux gaming is getting faster because Windows APIs are becoming Linux kernel features
(www.xda-developers.com)
this post was submitted on 14 May 2026
129 points (100.0% liked)
Linux
13668 readers
309 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Why? Lots of people are using wine.
That's like saying we shouldn't be including modules for reverse engineered hardware that only benefits that company
@auzy1 @Scoopta My problem with wine is that it can not work for most programs.
Depends. For games it's usage is fairly common these days. It's transparent in steam
It's not perfect for apps but it does a surprisingly good job
No, that's not quite the same thing, I fundamentally don't think it should be Linux's goal to be a good windows emulator. It's fine if wine exists and people use wine for that, but I don't think that should be a goal for the kernel, this starts pushing into that territory. Hardware support very much is the Kernel's job and modules which benefit it should be there if it's meaningful
Except this is a scheduler issue from my understanding.
You can make the argument to put everything into user space, but it's a performance issue.
One of the growing huge applications of linux these days is gaming, which depends hugely on performance, and almost every gamer out there is likely using wine (generally, without even realising it).
It's not a scheduler issue, it's a windows apps do thread synchronization differently to linux apps. Additionally fsync in the vast majority of use cases works just fine, the article notes most performance comparisons are against vanilla wine synchronization, i.e. without fsync or even esync. Regardless I still don't think the kernel should be emulating windows scheduling behavior.