[PATCH v4] dma-buf: Add ioctls to allow userspace to flush

On Wed, Aug 26, 2015 at 11:32:30AM -0300, Tiago Vignatti wrote: > On 08/26/2015 09:58 AM, Daniel Vetter wrote: > >The other is that right now there's no user nor implementation in sight > >which actually does range-based flush optimizations, so I'm pretty much > >expecting we'll get it wrong.

[PATCH v4] dma-buf: Add ioctls to allow userspace to flush

On 08/26/2015 04:32 PM, Tiago Vignatti wrote: > On 08/26/2015 09:58 AM, Daniel Vetter wrote: >> The other is that right now there's no user nor implementation in sight >> which actually does range-based flush optimizations, so I'm pretty much >> expecting we'll get it wrong. Maybe instead we

[PATCH v4] dma-buf: Add ioctls to allow userspace to flush

> 26 aug 2015 kl. 16:58 skrev Tiago Vignatti : > >> On 08/26/2015 11:51 AM, Daniel Vetter wrote: >>> On Wed, Aug 26, 2015 at 11:32:30AM -0300, Tiago Vignatti wrote: On 08/26/2015 09:58 AM, Daniel Vetter wrote: The other is that right now there's no user nor implementation in sight

[PATCH v4] dma-buf: Add ioctls to allow userspace to flush

On Wed, Aug 26, 2015 at 02:28:30PM +0200, Thomas Hellstrom wrote: > On 08/26/2015 02:10 PM, Daniel Vetter wrote: > > On Wed, Aug 26, 2015 at 08:49:00AM +0200, Thomas Hellstrom wrote: > >> Hi, Tiago. > >> > >> On 08/26/2015 02:02 AM, Tiago Vignatti wrote: > >>> From: Daniel Vetter > >>> > >>> The

[PATCH v4] dma-buf: Add ioctls to allow userspace to flush

On 08/26/2015 02:10 PM, Daniel Vetter wrote: > On Wed, Aug 26, 2015 at 08:49:00AM +0200, Thomas Hellstrom wrote: >> Hi, Tiago. >> >> On 08/26/2015 02:02 AM, Tiago Vignatti wrote: >>> From: Daniel Vetter >>> >>> The userspace might need some sort of cache coherency management e.g. when >>> CPU

[PATCH v4] dma-buf: Add ioctls to allow userspace to flush

On Wed, Aug 26, 2015 at 08:49:00AM +0200, Thomas Hellstrom wrote: > Hi, Tiago. > > On 08/26/2015 02:02 AM, Tiago Vignatti wrote: > > From: Daniel Vetter > > > > The userspace might need some sort of cache coherency management e.g. when > > CPU > > and GPU domains are being accessed through

[PATCH v4] dma-buf: Add ioctls to allow userspace to flush

On 08/26/2015 11:51 AM, Daniel Vetter wrote: > On Wed, Aug 26, 2015 at 11:32:30AM -0300, Tiago Vignatti wrote: >> On 08/26/2015 09:58 AM, Daniel Vetter wrote: >>> The other is that right now there's no user nor implementation in sight >>> which actually does range-based flush optimizations, so I'm

[PATCH v4] dma-buf: Add ioctls to allow userspace to flush

On 08/26/2015 09:58 AM, Daniel Vetter wrote: > The other is that right now there's no user nor implementation in sight > which actually does range-based flush optimizations, so I'm pretty much > expecting we'll get it wrong. Maybe instead we should go one step further > and remove the range from

[PATCH v4] dma-buf: Add ioctls to allow userspace to flush

Hi, Tiago. On 08/26/2015 02:02 AM, Tiago Vignatti wrote: > From: Daniel Vetter > > The userspace might need some sort of cache coherency management e.g. when CPU > and GPU domains are being accessed through dma-buf at the same time. To > circumvent this problem there are begin/end coherency

[PATCH v4] dma-buf: Add ioctls to allow userspace to flush

From: Daniel Vetter The userspace might need some sort of cache coherency management e.g. when CPU and GPU domains are being accessed through dma-buf at the same time. To circumvent this problem there are begin/end coherency markers, that forward directly to existing