[enhancement] android hwc overlay could optimize movement of surfaces without buffer update
Bug #1339749 reported by
Kevin DuBois
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Won't Fix
|
Low
|
Kevin DuBois | ||
mir-android-platform |
New
|
Undecided
|
Unassigned | ||
mir (Ubuntu) |
Won't Fix
|
Low
|
Unassigned |
Bug Description
Currently, we check in the hwc code that a buffer has changed from the previous commit to avoid submitting the same thing to the screen twice. This does not factor in changes to the the screen positioning. If it did, we could optimize a few more scenarios using 2d acceleration.
This won't cause rendering glitches, just a bit worse performance in some non-critical-path scenarios.
Changed in mir: | |
status: | New → Confirmed |
status: | Confirmed → In Progress |
Changed in mir: | |
milestone: | none → 0.8.0 |
Changed in mir: | |
milestone: | 0.8.0 → 0.9.0 |
Changed in mir: | |
milestone: | 0.9.0 → 0.10.0 |
Changed in mir: | |
milestone: | 0.10.0 → none |
Changed in mir: | |
status: | Confirmed → In Progress |
milestone: | none → 0.13.0 |
Changed in mir: | |
milestone: | 0.13.0 → 0.14.0 |
summary: |
- android hwc overlay could optimize movement of surfaces without buffer - update + [enhancement] android hwc overlay could optimize movement of surfaces + without buffer update |
tags: | added: enhancement |
tags: | added: overlays |
Changed in mir: | |
milestone: | 0.14.0 → 0.15.0 |
Changed in mir: | |
milestone: | 0.15.0 → 0.16.0 |
Changed in mir: | |
milestone: | 0.16.0 → 0.17.0 |
Changed in mir: | |
milestone: | 0.17.0 → 0.18.0 |
Changed in mir: | |
importance: | Medium → Low |
Changed in mir (Ubuntu): | |
importance: | Undecided → Low |
Changed in mir: | |
status: | Confirmed → Triaged |
Changed in mir (Ubuntu): | |
status: | New → Triaged |
To post a comment you must log in.
raised priority to medium because it affects the touchspot rendering