Re: [PATCH 13/24] dma-buf: drop the DAG approach for the dma_resv object

On Tue, Jan 04, 2022 at 04:08:20PM +0100, Christian König wrote: > Am 22.12.21 um 22:43 schrieb Daniel Vetter: > > On Tue, Dec 07, 2021 at 01:34:00PM +0100, Christian König wrote: > > > So far we had the approach of using a directed acyclic > > > graph with the dma_resv obj. > > > > > > This

Re: [PATCH 13/24] dma-buf: drop the DAG approach for the dma_resv object

Am 22.12.21 um 22:43 schrieb Daniel Vetter: On Tue, Dec 07, 2021 at 01:34:00PM +0100, Christian König wrote: So far we had the approach of using a directed acyclic graph with the dma_resv obj. This turned out to have many downsides, especially it means that every single driver and user of this

Re: [PATCH 13/24] dma-buf: drop the DAG approach for the dma_resv object

On Tue, Dec 07, 2021 at 01:34:00PM +0100, Christian König wrote: > So far we had the approach of using a directed acyclic > graph with the dma_resv obj. > > This turned out to have many downsides, especially it means > that every single driver and user of this interface needs > to be aware of

[PATCH 13/24] dma-buf: drop the DAG approach for the dma_resv object

So far we had the approach of using a directed acyclic graph with the dma_resv obj. This turned out to have many downsides, especially it means that every single driver and user of this interface needs to be aware of this restriction when adding fences. If the rules for the DAG are not followed