3 ms·

Sure, but then you still don't have V-Sync, which causes terrible and easily noticeable tearing on almost anything (at least in the case of Nvidia, it seems to

by sspiff 9y ago

Sure, but then you still don't have V-Sync, which causes terrible and easily noticeable tearing on almost anything (at least in the case of Nvidia, it seems to be much better with AMD from my annecdotal testing). I doubt Apple would find tearing acceptable on their products, honestly.

DiabloD3 9y ago
That isn't related to dma-buf-type usage, though. That would be purely one of the drivers not signalling the end of the frame to the other (since all graphical APIs have suitable methods for this, and WDDM itself natively understands the concept). Also, in Windows 10, the window manager's compositor (equivalent thereof) does all the event signaling fine; ie, you could easily have a situation where a game is rendered on one GPU, displayed on the other, and the display GPU + monitor has VESA Adaptive-sync enabled, and the game correctly triggers new sync windows as if it had been running on the same GPU. Does this work in practice? Who knows, but its supposed to, especially with fixes that 1703 and 1709 added.
- mrec 9y ago
  Is this intended/expected to work on desktop setups with discrete GPUs too? I believe Optimus et al were always laptop-only, but some desktop users might care about heat/power/fan noise.
  - DiabloD3 9y ago
    It's expected to work. I've tested it on mine, Haswell i7's own iGPU, and a full sized GCN Radeon, with a game rendering on the Radeon but displaying on the iGPU. Multi-monitor setup with 2 on the Radeon (normally all 3) and 1 on the iGPU, seemed to work fine. No real visible lag either, from what I could tell with limited testing.
  - rasz 9y ago
    Works on desktop just fine. For example Pentium G3258 integrated GPU forwarding fullhd over VGA rendered on ancient Nvidia 7900GS (old, but still 2-4x faster than integrated intel). Overhead was ~10-30% compared to direct monitor connection to nvidia card.

by sspiff 9y ago

DiabloD3 9y ago

That isn't related to dma-buf-type usage, though. That would be purely one of the drivers not signalling the end of the frame to the other (since all graphical APIs have suitable methods for this, and WDDM itself natively understands the concept). Also, in Windows 10, the window manager's compositor (equivalent thereof) does all the event signaling fine; ie, you could easily have a situation where a game is rendered on one GPU, displayed on the other, and the display GPU + monitor has VESA Adaptive-sync enabled, and the game correctly triggers new sync windows as if it had been running on the same GPU. Does this work in practice? Who knows, but its supposed to, especially with fixes that 1703 and 1709 added.

mrec 9y ago
Is this intended/expected to work on desktop setups with discrete GPUs too? I believe Optimus et al were always laptop-only, but some desktop users might care about heat/power/fan noise.
- DiabloD3 9y ago
  It's expected to work. I've tested it on mine, Haswell i7's own iGPU, and a full sized GCN Radeon, with a game rendering on the Radeon but displaying on the iGPU. Multi-monitor setup with 2 on the Radeon (normally all 3) and 1 on the iGPU, seemed to work fine. No real visible lag either, from what I could tell with limited testing.
- rasz 9y ago
  Works on desktop just fine. For example Pentium G3258 integrated GPU forwarding fullhd over VGA rendered on ancient Nvidia 7900GS (old, but still 2-4x faster than integrated intel). Overhead was ~10-30% compared to direct monitor connection to nvidia card.