Hi Yuri
El mié, 30-11-2016 a las 15:02 +0200, Yuri Benditovich escribió:
> Hello Javier,
>
> After implementing the pushing thread in current qxl-wddm-dod I
> measure the CPU consumption in PresentDisplayOnly call and in the
> thread on pushing drawables to the device. The results show that the
>
As already stated by Javier the difference was not the CPU usage but user
experience.
I think that mainly the Windows engine is free to do its own job while our
driver complete
the operation. Looking at Windows calls to our driver looks like Windows keep
another
frame buffer and periodically
Hello Javier,
After implementing the pushing thread in current qxl-wddm-dod I measure the
CPU consumption in PresentDisplayOnly call and in the thread on pushing
drawables to the device. The results show that the time to push drawables
is negligible in relation to time of copying dirty rects to th
> Hello Yuri
> El vie, 25-11-2016 a las 01:08 +0200, Yuri Benditovich escribió:
> > I'm porting to [qxl-wddm-dod] set of flexvdi changes
>
> > related to execution of ' present display only' events
>
> > in separate thread. There are 2 questions below I'd like to ask and k now
> > your opinion.
Hello Yuri
El vie, 25-11-2016 a las 01:08 +0200, Yuri Benditovich escribió:
> I'm porting to [qxl-wddm-dod] set of flexvdi changes
> related to execution of 'present display only' events
> in separate thread. There are 2 questions below I'd like to ask and
> know your opinion.
>
> I see there 2 as
I'm porting to [qxl-wddm-dod] set of flexvdi changes
related to execution of 'present display only' events
in separate thread. There are 2* questions below* I'd like to ask and know
your opinion.
I see there 2 aspects:
- reliability
- performance
*Reliability:*
I see in flexvdi mailing list exist
