standards-proposals
standards-proposals copied to clipboard
codeplaysoftware
Repository for publicly sharing proposals in various standards groups
The current interface for affinity queries supports querying latency, bandwidth, capacity and power consumption. However, there is currently no way to query for the relationship between an execution resource and...
Whilst adding the `bulk_execution_affinity` properties to the paper there was some discussion about who should be responsible for specifying the properties, the execution context, the executor or both. **(taken from...
Split execution and memory resources within topology. Make execution resources iterable. Reduce scope by removing specific execution context, which was not needed for affinity exploration. Tied current naming and discussion...
I wonder if we need a memory_context similar to the execution_context that has the allocation capabilities, e.g, you retrieve an allocator that is bound to the memory resource. This allows...
There was feedback from Jacksonville that we should start looking into how to support dynamic device discovery, where an execution resource within a system may become available or unavailable during...
Feedback from some users after trying out the placeholder accessors seems to indicate that they should be default constructible, and that the buffer should be assigned later during the requirement...
Metadata
Owner
Metadata
Repository for publicly sharing proposals in various standards groups