I was wondering whether its possible to keep the contents of the texture cache alive for consecutive kernel calls (without flushing and reloading). In this way for many applications I need not reload texture cache where the kernel is invoked repeatedly or iteratively as a mean of global synchronization.
I also understand that for some application if the memory region accessed by the texture cache changes during each kernel call then its better to flush and reload the texture cache for each kernel call.
But I am looking at other application where the content of texture region remains the same for successive kernel calls.
Any suggestions or possibilities ?