[RFC PATCH 3/4] winevulkan: Add support for named video resources.

[Paul Gofman]

On 5/4/21 23:05, Derek Lesho wrote:
> On 5/4/21 3:56 PM, Paul Gofman wrote:
>
>>
>> Can't those handles be just, say, mapping handles with the specific
>> resource description, fd etc. data filled in and interpreted by the
>> interested graphic layers?
> The main reason why this wouldn't be feasible is the edge case of a
> process which creates a shared resource then shuts down.  The process
> into which the resource was copied would still have an open handle to
> the mapping, but the mapping wouldn't hold a reference to the actual
> resource.

If a separate process (say, ntoskrnl.exe) can hold all the required data
independently of the process which created the shared resource, can't
shared memory hold that instead (possibly using some other global
[named?] objects already supported by wineserver?