Am 24.08.2016 um 17:42 schrieb Marek Olšák: > On Wed, Aug 24, 2016 at 5:31 PM, Roland Scheidegger <srol...@vmware.com> > wrote: >> Am 24.08.2016 um 11:22 schrieb Marek Olšák: >>> On Wed, Aug 24, 2016 at 2:02 AM, Roland Scheidegger <srol...@vmware.com> >>> wrote: >>>> I admit I'm not familiar with the interopability stuff. >>>> But how is the coherency stuff handled after you get the handle? >>>> Does this also work if you've got multiple users of resource_get_handle? >>> >>> Basically, radeonsi just makes sure the resource contents are >>> decompressed before sharing and flushes the context. After that, the >>> resource is ready for sharing and can be re-exported any number of >>> times. >>> >> >> Ok. I was just thinking of situations where you could share the same >> resource between more than two contexts, and not all having the same >> requirements (e.g. decompression not always be necessary). >> But if the api is flexible enough to handle such things it should be ok. > > All resources are trivially sharable as long as they are managed by > the same pipe_screen. This change is for the kind of sharing that > involves an out-of-tree driver component (e.g. OpenCL) or a different > process (the EGL DMABUF extension). >
So you always need to decompress for that? Roland _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
