[enhancement] add a toggle for "unsyncing" on eglswapinterval 0
Bug #1304513 reported by
kevin gunn
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Expired
|
Medium
|
Unassigned |
Bug Description
at the sprint in London, we discussed that the mechanism for the mesa clients is currently to still "sync" on the compositor (even tho its not sync'd on vsync) in order to avoid tearing.
however, its common for clients to accept tearing. Since we do have the ability to keep clients non-tearing with swapinterval 0 we shouldn't throw it out, however we should probably add another toggle in the code to allow for tearing as well with swapinterval 0.
tags: | added: enhancement |
Changed in mir: | |
importance: | High → Medium |
To post a comment you must log in.
just for further clarification - i would like this as its useful in performance analysis and inferring load/idle times & debugging vsync issues. I believe another way to look at this is to enable "single buffering" as an option, which means there would need to be an optional config (arch change) to allow for the compositor to read from a buffer that the client is writing into