Lines Matching full:memory
48 This extension extends the memory objects introduced with EXT_memory_object
49 to allow existing textures and buffers to be migrated to an imported memory
59 void GetMemoryObjectDetachedResourcesuivNV(uint memory,
65 void ResetMemoryObjectParameterNV(uint memory,
69 uint memory,
73 uint memory,
79 uint memory,
83 uint memory,
125 (Memory Objects)
127 Add a new sections after 6.2 (Memory object parameters)
129 6.3 Attaching memory to existing resources
132 a memory object to an existing resource (buffer or texture). The
133 memory region size and offset alignment required by a resource can be
136 memory object and the used offset for a resource can be queried by
139 If a resource which has memory attached is resized, the attached memory
141 which has memory attached is deleted, the attached memory will first be
144 memory object. The incarnation counter can be queried by
146 memory object.
150 void GetMemoryObjectDetachedResourcesuivNV(uint memory,
158 in <params> for memory object <memory>. It will return <count> items
162 generated by GetMemoryObjectDetachedResourcesuivNV if <memory> is 0.
163 An INVALID_OPERATION error is generated if <memory> names a valid
164 memory object which has no associated memory. An INVALID_VALUE error
178 void ResetMemoryObjectParameterNV(uint memory,
183 for memory object <memory>. An INVALID_VALUE error is generated by
184 ResetMemoryObjectParameterNV if <memory> is 0. An INVALID_OPERATION
185 error is generated if <memory> names a valid memory object which has
186 no associated memory. An INVALID_VALUE error is generated if <pname>
194 6.2.2 Attaching a memory object to a buffer object
199 uint memory,
203 uint memory,
206 will attach a region of a memory object to a buffer object. For
210 object. <memory> and <offset> define a region of memory that will
214 which values of <offset> are valid for a given memory object and buffer
217 which created the resource which <memory> refers to. If an invalid
220 NamedBufferAttachMemoryNV if <memory> is 0. An INVALID_OPERATION error
221 is generated if <memory> names a valid memory object which has no
222 associated memory. An INVALID_OPERATION error is generated if the
233 8.20 Attaching a memory object to a texture image
238 uint memory,
242 uint memory,
245 will attach a region of a memory object to a texture. For
251 the name of the texture. <memory> and <offset> define a region of
252 memory that will replace the data store for <texture>. The content of
256 given memory object and texture parameter combination. These
259 which <memory> refers to. If an invalid offset is specified an
261 by TexAttachMemoryNV and TextureAttachMemoryNV if <memory> is 0. An
262 INVALID_OPERATION error is generated if <memory> names a valid memory
263 object which has no associated memory.
291 // allocate memory within vulkan and import it as specified in
294 // attach imported vulkan memory
312 // if we have multiple memory objects
339 // narrow down search which memory object was affected
364 // mark its memory as available again
383 2) Should binding memory only work on immutable resources?
393 when they are persistent. When memory is attached resource must be
398 RESOLVED: TextureViews inherit the memory state.
403 when memory is attached and must be queried afterwards.
405 6) Should we support resources that were migrated to host memory by driver?
407 RESOLVED: Yes, but the attached memory is independ from this state.
415 RESOLVED: A memory object becomes resident if at least one attached