LocalityHint
LocalityHint
Section titled “LocalityHint”#include <xalgospp/scheduling/task.hh>struct LocalityHintDefined in src/lib/xalgospp/scheduling/task.hh:55
Details for placement of a task on specific resources.
List of all members
Section titled “List of all members”| Name | Kind | Owner |
|---|---|---|
preferred_node |
variable |
Declared here |
memory_affinity_ptr |
variable |
Declared here |
memory_affinity_ptr_ptr |
variable |
Declared here |
Public Attributes
Section titled “Public Attributes”| Return | Name | Description |
|---|---|---|
numa_node_t |
preferred_node |
Indicate the NUMA node preference. |
const void * |
memory_affinity_ptr |
The physical page location if provided. |
const void *const * |
memory_affinity_ptr_ptr |
A pointer to the location. |
preferred_node
Section titled “preferred_node”numa_node_t preferred_node { }Defined in src/lib/xalgospp/scheduling/task.hh:59
Indicate the NUMA node preference.
memory_affinity_ptr
Section titled “memory_affinity_ptr”const void * memory_affinity_ptr { nullptr }Defined in src/lib/xalgospp/scheduling/task.hh:66
The physical page location if provided.
This will generally mean that there is a single static lookup where the data will always be.
memory_affinity_ptr_ptr
Section titled “memory_affinity_ptr_ptr”const void *const * memory_affinity_ptr_ptr { nullptr }Defined in src/lib/xalgospp/scheduling/task.hh:73
A pointer to the location.
For dynamic lookup, where the data may be in different places, the pointer to pointer can be used instead of the static option above.