The changed field in PA_SC_RASTER_CONFIG is pretty clear here: 0 - RB0 renders all pixels (default for single rb per pkr configs) 1 - RB0 renders rb_tile_id==1, RB1 renders rb_tile_id==0 2 - RB0 renders rb_tile_id==0, RB1 renders rb_tile_id==1 3 - RB1 renders all pixels
So you see that values 0 and 3 are for single RB or harvested configs. You need either 1 or 2 for full configs. Full configs can also use this to disable RBs if the bus can't handle too many transfers efficiently (e.g. dGPUs blitting to GTT). Marek On Wed, May 2, 2018 at 3:11 PM, Marek Olšák <mar...@gmail.com> wrote: > If you are shader-bound, you won't see any difference. In order to become > RB-bound, you need more work in RBs than shaders. Blending or MSAA might > help add that. > > Marek > > On Wed, May 2, 2018 at 5:31 AM, Michel Dänzer <mic...@daenzer.net> wrote: > >> On 2018-05-02 06:00 AM, Marek Olšák wrote: >> > From: Marek Olšák <marek.ol...@amd.com> >> > >> > This can result in 2x increase in performance on non-harvested Kaveris. >> >> FWIW, no difference with glxgears on my (non-harvested AFAIK) Kaveris, >> neither with amdgpu nor radeon. Should I try something else? >> >> Tested-by: Michel Dänzer <michel.daen...@amd.com> >> >> >> -- >> Earthling Michel Dänzer | http://www.amd.com >> Libre software enthusiast | Mesa and X developer >> > >
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
