blob: bb8e8f53bde28a8d6c6b1d82553505799b59ec9e (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
|
// Copyright 2017-2023 The Khronos Group Inc.
//
// SPDX-License-Identifier: CC-BY-4.0
include::{generated}/meta/{refprefix}VK_EXT_queue_family_foreign.adoc[]
=== Other Extension Metadata
*Last Modified Date*::
2017-11-01
*IP Status*::
No known IP claims.
*Contributors*::
- Lina Versace, Google
- James Jones, NVIDIA
- Faith Ekstrand, Intel
- Jesse Hall, Google
- Daniel Rakos, AMD
- Ray Smith, ARM
=== Description
This extension defines a special queue family,
ename:VK_QUEUE_FAMILY_FOREIGN_EXT, which can be used to transfer ownership
of resources backed by external memory to foreign, external queues.
This is similar to ename:VK_QUEUE_FAMILY_EXTERNAL_KHR, defined in
`apiext:VK_KHR_external_memory`.
The key differences between the two are:
* The queues represented by ename:VK_QUEUE_FAMILY_EXTERNAL_KHR must share
the same physical device and the same driver version as the current
slink:VkInstance.
ename:VK_QUEUE_FAMILY_FOREIGN_EXT has no such restrictions.
It can represent devices and drivers from other vendors, and can even
represent non-Vulkan-capable devices.
* All resources backed by external memory support
ename:VK_QUEUE_FAMILY_EXTERNAL_KHR.
Support for ename:VK_QUEUE_FAMILY_FOREIGN_EXT is more restrictive.
* Applications should expect transitions to/from
ename:VK_QUEUE_FAMILY_FOREIGN_EXT to be more expensive than transitions
to/from ename:VK_QUEUE_FAMILY_EXTERNAL_KHR.
include::{generated}/interfaces/VK_EXT_queue_family_foreign.adoc[]
=== Version History
* Revision 1, 2017-11-01 (Lina Versace)
** Squashed internal revisions
|
