[PATCH 3/4] modesetting: Implement a double-buffered shadow mode

Eric Anholt eric at anholt.net
Mon Jul 27 13:35:00 PDT 2015


Adam Jackson <ajax at redhat.com> writes:

> Server GPUs often have a VNC feature attached to allow remote console.
> The controller implementing this feature is usually not very powerful,
> and we can easily swamp it with work.  This is made somewhat worse by
> damage over-reporting the size of the dirty region, and a whole lot
> worse by applications (or shells) that update the screen with identical
> pixel content as was already there.
>
> Fix this by double-buffering the shadow fb, using memcmp to identify
> dirty tiles on each update pass.  Since both shadows are in host memory
> the memcmp is cheap, and worth it given the win in network bandwidth.
> The tile size is somewhat arbitrarily chosen to be one cacheline wide at
> 32bpp on Intel Core.
>
> By default we enable this behaviour for (a subset of) known server GPUs;
> the heuristic could use work.

I'm not opposed to this, but could the kernel driver let us know that
the GPU has this hardware VNC feature attached somehow?

This whole series appears to need some x-indent.sh treatment.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg-devel/attachments/20150727/34b8cd3c/attachment.sig>


More information about the xorg-devel mailing list