I don’t think Proton has anything special going on in that regard actually. It’s got DXVK and all the other stuff built-in, but for the synchronization primitives I think it just uses fsync just like Wine does, so this might be interesting…
fsync isn’t part of wine, which is what they are referring to.
Fsync and Esync are both inaccurate representations, and while they help performance in many places (particularly games), they break other things. Hence, while useful, they never got mainlined.
NTsync is an accurate reimplementation, hence why this functionality will finally become part of wine proper.
Yup. And it’ll be a huge improvement overall to simply have both performance and accuracy in one, and not have to pick one or the other, regardless of what application is being run.
I don’t think Proton has anything special going on in that regard actually. It’s got DXVK and all the other stuff built-in, but for the synchronization primitives I think it just uses fsync just like Wine does, so this might be interesting…
fsync isn’t part of wine, which is what they are referring to.
Fsync and Esync are both inaccurate representations, and while they help performance in many places (particularly games), they break other things. Hence, while useful, they never got mainlined.
NTsync is an accurate reimplementation, hence why this functionality will finally become part of wine proper.
I see. Either way there are some substantial improvements over fsync in some cases, so it should benefit Proton as well.
Yup. And it’ll be a huge improvement overall to simply have both performance and accuracy in one, and not have to pick one or the other, regardless of what application is being run.