[Mesa-dev] [PATCH 0/7] i965 L3 caching and pull constant improvements.

[Kenneth Graunke]

On Wednesday, January 28, 2015 01:14:08 PM Syrja, Harri wrote:
> Hi Kenneth,
> 
> Constant cache could and should allocate to separate region in $L3. The main point of having separate constant region is to avoid texture data trashing due to pulled constants load. In optimal solution constant region is allocated only when shader uses pull constants, but that is not so easy as the $L3 config reg is not part of per constant regs. 
> 
> BR,
> Harri

I agree that constants and textures /could/ be allocated to a separate region
of $L3, but I haven't found any evidence in the documentation to confirm that.

It looks like you can set it up that way on Haswell (and we don't), but on
other chips, everything I've found suggests that read-only clients are lumped
together in the same region...

--Ken
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.freedesktop.org/archives/mesa-dev/attachments/20150128/9c5ae0d3/attachment.sig>