[lkml]   [2019]   [Apr]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: dynamic DMA-buf sharing between devices
On top of those I have 6 more patches in the pipeline to enable VRAM P2P 
with DMA-buf.

So that is not the end of the patch set :)


Am 17.04.19 um 15:52 schrieb Chunming Zhou:
> Thanks Christian, great job. I will verify it this week when I finish my
> current work on hand.
> -David
> 在 2019/4/17 2:38, 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.
>> Please review and/or comment,
>> Christian.
>> _______________________________________________
>> dri-devel mailing list

 \ /
  Last update: 2019-04-17 16:00    [W:0.252 / U:0.848 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site