Re: [Mesa-dev] [PATCH 2/3] radv: only copy the dynamic states that changed

2017-09-18 Thread Samuel Pitoiset
On 09/15/2017 05:40 PM, Fredrik Höglund wrote: On Thursday 14 September 2017, Samuel Pitoiset wrote: On 09/13/2017 06:34 PM, Fredrik Höglund wrote: On Wednesday 13 September 2017, Samuel Pitoiset wrote: When binding a new pipeline, we applied all dynamic states without checking if they

Re: [Mesa-dev] [PATCH 2/3] radv: only copy the dynamic states that changed

2017-09-15 Thread Fredrik Höglund
On Thursday 14 September 2017, Samuel Pitoiset wrote: > > On 09/13/2017 06:34 PM, Fredrik Höglund wrote: > > On Wednesday 13 September 2017, Samuel Pitoiset wrote: > >> When binding a new pipeline, we applied all dynamic states > >> without checking if they really need to be re-emitted. This > >>

Re: [Mesa-dev] [PATCH 2/3] radv: only copy the dynamic states that changed

2017-09-14 Thread Samuel Pitoiset
On 09/13/2017 06:34 PM, Fredrik Höglund wrote: On Wednesday 13 September 2017, Samuel Pitoiset wrote: When binding a new pipeline, we applied all dynamic states without checking if they really need to be re-emitted. This doesn't seem to be useful for the meta operations because only the

Re: [Mesa-dev] [PATCH 2/3] radv: only copy the dynamic states that changed

2017-09-13 Thread Fredrik Höglund
On Wednesday 13 September 2017, Samuel Pitoiset wrote: > When binding a new pipeline, we applied all dynamic states > without checking if they really need to be re-emitted. This > doesn't seem to be useful for the meta operations because only > the viewports/scissors are updated. > > This should

[Mesa-dev] [PATCH 2/3] radv: only copy the dynamic states that changed

2017-09-13 Thread Samuel Pitoiset
When binding a new pipeline, we applied all dynamic states without checking if they really need to be re-emitted. This doesn't seem to be useful for the meta operations because only the viewports/scissors are updated. This should reduce the number of commands added to the IB when a new graphics