<html><head></head><body><div class="ydp3f6c515cyahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div> <div><span style="color: rgb(38, 40, 42); font-size: 13px;">> In order to display anything on the screen the video card needs an array</span><br></div><div id="ydp3f6c515cyahoo_quoted_3126589928" class="ydp3f6c515cyahoo_quoted"><div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;"><div><div dir="ltr">>of data given color of each pixel. This is usually called "framebuffer" <br clear="none">>because it buffers data for one frame of video.<br clear="none"><br>Thank you for the enlightening explanation! An unrelated question: IIUC the framebuffer is a shared memory in userspace. I see a huge amount of memory (around 1GB) in the kernel space related to sth called the GEM layer. Why is this large allocation needed?<br clear="none"><br clear="none">> When you request "dpms off" all this does is tell monitor to turn off the <br clear="none">> light and save power. Everything that normally be drawn will still be <br clear="none">> drawn, as you can verify using x11vnc and vncviewer.<br clear="none"><br>How does the interactive input cause screen reactivation? Is it signaled in software? If yes, perhaps the signal could be hidden by some small changes in the software to prevent the reactivation.<br><br clear="none">> From the point of view of a benchmark you need to be very careful not <br clear="none">> alter the task, as modern systems love to optimize.<br clear="none"><br>I will have to do some approximations using a combination of the processor and IMC counters.</div></div> </div> </div></div></body></html>