jcstress: Accept non-sequential CPU ID topologies

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Fixed
    • Priority: P4
    • None
    • Affects Version/s: None
    • Component/s: tools
    • None

      On some guest VMs / containers, sysfs only shows the subset of CPUs allocated for it. Current sysfs code and affinity handling code relies on CPU IDs to be consecutive. On those machines, sysfs parser fails and we fall back to naive topology.

      We can make it significantly better.

            Assignee:
            Aleksey Shipilev
            Reporter:
            Aleksey Shipilev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: