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

2018-08-14 Thread Samuel Pitoiset
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

2018-08-14 Thread Marek Olšák
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

2018-08-14 Thread Samuel Pitoiset
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

2018-07-31 Thread Marek Olšák
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. > >

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

2017-10-20 Thread Andres Rodriguez
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. We always hardcode the field to its maximum value, instead of attempt