Op 14-09-16 om 19:07 schreef Imre Deak: > While user space has control over the scheduling priority of its page > flipping thread, the corresponding work the driver schedules for MMIO > flips always runs from the generic system workqueue which has some > scheduling overhead due it being CPU bound. This would hinder an > application that wants more stringent guarantees over flip timing (to > avoid missing a flip at the next frame count). > > Fix this by scheduling the work from a dedicated, unbound workqueue > which provides for minimal scheduling latency. I think it should use the same wq as intel_atomic_commit, either page flip should use system_unbound_wq, or atomic_commit should use this one. ~Maarten _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
