Ok I see. I am not sure if it was good choice from VPG not to support dedicated region for constant cache, but if that is what it is there is little we can do for it.
Thank, Harri -----Original Message----- From: Kenneth Graunke [mailto:kenn...@whitecape.org] Sent: Wednesday, January 28, 2015 7:18 PM To: Syrja, Harri Cc: mesa-dev@lists.freedesktop.org; Francisco Jerez Subject: Re: [Mesa-dev] [PATCH 0/7] i965 L3 caching and pull constant improvements. 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 --------------------------------------------------------------------- Intel Finland Oy Registered Address: PL 281, 00181 Helsinki Business Identity Code: 0357606 - 4 Domiciled in Helsinki This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
