[cairo] [Patch] Limit the amount of shared memory that cairo-xcb uses

[Uli Schlachter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Am 30.01.2011 19:45, Chris Wilson wrote:
> I am personally in favour of not using SHM by default. Enabling any amount
> of SHM is likely to cause an issue somewhere and so needs to be managed by
> the client.

Uhm, what kind of issue would you expect? I can't really think of anything bad
that would happen from SHM.

> In effect the only time where we use SHM effectively automatically is for
> fallbacks. Where it is most useful is during pixel upload, and for that we
> need client participation and something akin to
> cairo_surface_create_similar_image() to allocate a SHM image (or fallback
> appropriately) which can be filled by the client.

cairo_surface_create_similar / _cairo_xcb_surface_create_similar already does
exactly this. (Mesh gradients always use SHM currently, too)

But why do you think we need client participation for SHM? It works just fine
currently without any magic on the client side.

[...]

Cheers,
Uli
- -- 
Sometimes the people that know software the best are the ones
that hate it the most.                                      -- infogulch
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBCAAGBQJNRcH8AAoJECLkKOvLj8sGw+YIALBp4f7IhVCaqnfQcS44+wNB
bHz9Jc6RXy+lbov4PcQVw0o97vPWj78FH4kH3hHcY/VYQ3uoowcBg4gfNL894wHC
WPXcCBqR8rfJhRuusfe67MXbMyvobNFU0t8nQN0Q52nJUcqpzbXjbthpPal5zBQt
nvyRYBXGvBOPr4swE6Cq9IXbUyfM0mqdtxfnuGkXxYGPeguEuySq9hqow4rqrXCa
G8peZAVM2nzFav7qtVBOFE70SpbKc30I0T/uKm7GaANx+xMOsZn8jUX4dqd+LsSH
ayORgoCmxPZBiuix02RoJW81XM3Tc7cxjPFtWIZ8WnM3kVJVwhjbNR4uiohu8es=
=wuXM
-----END PGP SIGNATURE-----