You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, TasksetCtx::next() just returns the next core numerically.
However, cores IDs aren't split nicely across numa nodes. For example on the cloudlab c220g1, this is how CPUs are spread across numa nodes, per lscpu:
NUMA node0 CPU(s): 0-7,16-23
NUMA node1 CPU(s): 8-15,24-31
Something should be added to TasksetCtx allow it to only choose cores from a specified set of NUMA nodes.
The text was updated successfully, but these errors were encountered:
Currently, TasksetCtx::next() just returns the next core numerically.
However, cores IDs aren't split nicely across numa nodes. For example on the cloudlab c220g1, this is how CPUs are spread across numa nodes, per lscpu:
Something should be added to TasksetCtx allow it to only choose cores from a specified set of NUMA nodes.
The text was updated successfully, but these errors were encountered: