search for: bindless

Unfortuantely we don't know if a particular load is a real 2d image (as would be a cube face or 2d array element), or a layer of a 3d image. Since we pass in the TIC reference, the instruction's type has to match what's in the TIC (experimentally). In order to properly support bindless images, this also can't be done by looking at the current bindings and generating appropriate code. As a result all plain 2d loads are converted into a pair of 2d/3d loads, with appropriate predicates to ensure only one of those actually executes, and the values are all merged in. This goes s...

Hello, This question is in the context of Tesla / Fermi generations, which have explicit bindings for textures / samplers. It might also apply to Kepler+, not quite as sure due to the bindless nature. I've been trying to understand how the TLD operation works (which is used to implement texelFetch in GLSL). It does not appear to the op takes an explicit sampler id at all (unlike all the other texturing operations). In unlinked TSC mode (i.e. method 0x1234 == 0), my observation is th...

...eah, pretty much what we have in mind on the i915 side too. I didn't look > too closely at your patches, so just a few high level comments on your rfc > here. > > > I will try to explain why I think we should support the explicit model as well. > > > > > > 1. Bindless graphics > > > > Bindless graphics is a central concept when trying to reduce the OpenGL driver > > overhead. The idea is that the application can bind a large set of buffers to > > the working set up front using extensions such as GL_ARB_bindless_texture, and > > th...

...> > On Thu, Mar 01, 2018 at 11:47:18PM -0500, Ilia Mirkin wrote: >> Hello, >> >> This question is in the context of Tesla / Fermi generations, which >> have explicit bindings for textures / samplers. It might also apply to >> Kepler+, not quite as sure due to the bindless nature. >> >> I've been trying to understand how the TLD operation works (which is >> used to implement texelFetch in GLSL). It does not appear to the op >> takes an explicit sampler id at all (unlike all the other texturing >> operations). In unlinked TSC mode (i....

...with the > implicit paradigm. Yeah, pretty much what we have in mind on the i915 side too. I didn't look too closely at your patches, so just a few high level comments on your rfc here. > I will try to explain why I think we should support the explicit model as well. > > > 1. Bindless graphics > > Bindless graphics is a central concept when trying to reduce the OpenGL driver > overhead. The idea is that the application can bind a large set of buffers to > the working set up front using extensions such as GL_ARB_bindless_texture, and > they remain resident until...

...I hope that helps, - Andy On Thu, Mar 01, 2018 at 11:47:18PM -0500, Ilia Mirkin wrote: > Hello, > > This question is in the context of Tesla / Fermi generations, which > have explicit bindings for textures / samplers. It might also apply to > Kepler+, not quite as sure due to the bindless nature. > > I've been trying to understand how the TLD operation works (which is > used to implement texelFetch in GLSL). It does not appear to the op > takes an explicit sampler id at all (unlike all the other texturing > operations). In unlinked TSC mode (i.e. method 0x1234 ==...

...we have in mind on the i915 side too. I didn't look >> too closely at your patches, so just a few high level comments on your rfc >> here. >> >>> I will try to explain why I think we should support the explicit model as well. >>> >>> >>> 1. Bindless graphics >>> >>> Bindless graphics is a central concept when trying to reduce the OpenGL driver >>> overhead. The idea is that the application can bind a large set of buffers to >>> the working set up front using extensions such as GL_ARB_bindless_texture, and &...

...don't seek to change any of that. My proposal aims at allowing some drm drivers to operate in explicit sync mode to get maximal performance, while still remaining fully compatible with the implicit paradigm. I will try to explain why I think we should support the explicit model as well. 1. Bindless graphics Bindless graphics is a central concept when trying to reduce the OpenGL driver overhead. The idea is that the application can bind a large set of buffers to the working set up front using extensions such as GL_ARB_bindless_texture, and they remain resident until the application releases...