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
If I use taskset to restrict the cores available to Realm, it will correctly abide by this restriction when creating the processors, but the query API will wrongfully report that all cores are available.
Right, because the resource discovery does not read the cpu core map of the current process. I am working on a branch https://gitlab.com/StanfordLegion/legion/-/commits/topology, which will unify the topology discovery and it can be used by core and numa modules, as well as coremap creation. The bug will be fixed in that branch.
If I use
taskset
to restrict the cores available to Realm, it will correctly abide by this restriction when creating the processors, but the query API will wrongfully report that all cores are available.Unconstrained execution
Constrained execution
The text was updated successfully, but these errors were encountered: