Yeah it works, but you need to know what is the maximum fps a specific application can handle - so not scalable.
Workaround 2:
Didn't help in case of eglplasma
In any case, the cpu usage is caused by the driver, dri_flush specifically (actually looks like a bunch of drmCommandWriteRead->drmIoctl so perhaps the time is actually spent in the kernel driver.
Workaround 1:
Yeah it works, but you need to know what is the maximum fps a specific application can handle - so not scalable.
Workaround 2:
Didn't help in case of eglplasma
In any case, the cpu usage is caused by the driver, dri_flush specifically (actually looks like a bunch of drmCommandWrite Read->drmIoctl so perhaps the time is actually spent in the kernel driver.