Re: [Mesa-dev] [PATCH 2/3] radv: hardcode shader WAVE_LIMIT to the maximum value

On 8/14/18 5:46 PM, Marek Olšák wrote: On Tue, Aug 14, 2018, 8:28 AM Samuel Pitoiset > wrote: On 8/1/18 5:12 AM, Marek Olšák wrote: > On Fri, Oct 20, 2017 at 4:34 PM, Andres Rodriguez mailto:andre...@gmail.com>> wrote: >> When WAVE_LIMIT

Re: [Mesa-dev] [PATCH 2/3] radv: hardcode shader WAVE_LIMIT to the maximum value

On Tue, Aug 14, 2018, 8:28 AM Samuel Pitoiset wrote: > > > On 8/1/18 5:12 AM, Marek Olšák wrote: > > On Fri, Oct 20, 2017 at 4:34 PM, Andres Rodriguez > wrote: > >> When WAVE_LIMIT is set, a submission will opt-in for SPI based resource > >> scheduling. Because this mechanism is cooperative, we

Re: [Mesa-dev] [PATCH 2/3] radv: hardcode shader WAVE_LIMIT to the maximum value

On 8/1/18 5:12 AM, Marek Olšák wrote: On Fri, Oct 20, 2017 at 4:34 PM, Andres Rodriguez wrote: When WAVE_LIMIT is set, a submission will opt-in for SPI based resource scheduling. Because this mechanism is cooperative, we must ensure that all submissions have this field set, otherwise they wil

Re: [Mesa-dev] [PATCH 2/3] radv: hardcode shader WAVE_LIMIT to the maximum value

On Fri, Oct 20, 2017 at 4:34 PM, Andres Rodriguez wrote: > When WAVE_LIMIT is set, a submission will opt-in for SPI based resource > scheduling. Because this mechanism is cooperative, we must ensure that > all submissions have this field set, otherwise they will bypass resource > arbitration. > >