[lkml]   [2019]   [Apr]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: dynamic DMA-buf sharing between devices
Am 18.04.19 um 11:13 schrieb Daniel Vetter:
> On Tue, Apr 16, 2019 at 08:38:29PM +0200, Christian König wrote:
>> Hi everybody,
>> core idea in this patch set is that DMA-buf importers can now provide an optional invalidate callback. Using this callback and the reservation object exporters can now avoid pinning DMA-buf memory for a long time while sharing it between devices.
>> I've already send out an older version roughly a year ago, but didn't had time to further look into cleaning this up.
>> The last time a major problem was that we would had to fix up all drivers implementing DMA-buf at once.
>> Now I avoid this by allowing mappings to be cached in the DMA-buf attachment and so driver can optionally move over to the new interface one by one.
>> This is also a prerequisite to my patchset enabling sharing of device memory with DMA-buf.
> Ok, with the discussions and thinking I think this design is solid and
> should work out. Bunch of api and documentation polishing still to do, to
> make sure we have really clear semantics and as little room as possible
> for misunderstanding - refactoring a mess in dma-buf is a lot more tricky
> than just ttm, there's a lot more users.

Yeah, I'm pretty aware of that after changing all the users of the map
API to use a structure for the parameters.

Well at least it's not UAPI :)


> -Daniel

 \ /
  Last update: 2019-04-18 12:58    [W:0.222 / U:0.828 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site