Re: [PATCH] dma-buf: Refanctor reservation_object_add_shared_fence()

2018-01-30 Thread Christian König
Am 30.01.2018 um 13:50 schrieb Chris Wilson: Quoting Christian König (2018-01-30 12:26:05) Am 30.01.2018 um 10:32 schrieb Chris Wilson: Adding a shared fence to a reservation_object is currently split into two handlers, one to insert the fence into the existing array and the other to replace

Re: [PATCH] dma-buf: Refanctor reservation_object_add_shared_fence()

2018-01-30 Thread Chris Wilson
Quoting Christian König (2018-01-30 12:26:05) > Am 30.01.2018 um 10:32 schrieb Chris Wilson: > > Adding a shared fence to a reservation_object is currently split into > > two handlers, one to insert the fence into the existing array and the > > other to replace the existing array with a new larger

Re: [PATCH] dma-buf: Refanctor reservation_object_add_shared_fence()

2018-01-30 Thread Christian König
Am 30.01.2018 um 10:32 schrieb Chris Wilson: Adding a shared fence to a reservation_object is currently split into two handlers, one to insert the fence into the existing array and the other to replace the existing array with a new larger array. The first step in both of these routines involves

[PATCH] dma-buf: Refanctor reservation_object_add_shared_fence()

2018-01-30 Thread Chris Wilson
Adding a shared fence to a reservation_object is currently split into two handlers, one to insert the fence into the existing array and the other to replace the existing array with a new larger array. The first step in both of these routines involves scanning the existing array to decide if it can