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
At the time of this writing, only interactive configuration can select the set of cores.
I was thinking about a comma-separated list of cores similar to the one I suggested for tests in #72 , enabling both positive and negative selection.
This interacts with the CLI for #9; should we really try to build a unified CLI syntax to handle both core number selection and SMT/P-Core/E-Core enablement/disablement ?
Distant wishlist item: socket<n> and node<n> shortcuts for selecting respectively the cores of the given CPU socket and the cores of the given NUMA node, after parsing valid information from the ACPI SRAT for the latter. In the meantime, <m>-<n> range and <m>,<n>list syntaxes for selecting cores do the job for a sufficiently homogeneous set of computers.
The text was updated successfully, but these errors were encountered:
At the time of this writing, only interactive configuration can select the set of cores.
I was thinking about a comma-separated list of cores similar to the one I suggested for tests in #72 , enabling both positive and negative selection.
This interacts with the CLI for #9; should we really try to build a unified CLI syntax to handle both core number selection and SMT/P-Core/E-Core enablement/disablement ?
Distant wishlist item:
socket<n>
andnode<n>
shortcuts for selecting respectively the cores of the given CPU socket and the cores of the given NUMA node, after parsing valid information from the ACPI SRAT for the latter. In the meantime,<m>-<n>
range and<m>,<n>
list syntaxes for selecting cores do the job for a sufficiently homogeneous set of computers.The text was updated successfully, but these errors were encountered: