Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-42323

IRQBALANCE_BANNED_CPUS is not updated with isolated cpus when irq load balancing is disabled

XMLWordPrintable

    • Yes
    • Proposed
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, when the `globallyDisableIrqLoadBalancing` field was set to `true` in the `PerformanceProfile` object, the isolated CPUs were listed in the `IRQBALANCE_BANNED_CPULIST` variable instead of the `IRQBALANCE_BANNED_CPUS` variable. These variables are stored in `/etc/sysconfig/irqbalance`. Changing the value of the `globallyDisableIrqLoadBalancing` field from `true` to `false` did not update the `IRQBALANCE_BANNED_CPULIST` variable correctly. As a result, the number of CPUs available for load rebalancing did not increase because the isolated CPUs remained in the `IRQBALANCE_BANNED_CPULIST` variable. With this release, a fix ensures that isolated CPUs are now listed in the `IRQBALANCE_BANNED_CPUS` variable, so that the number of CPUs available for load rebalancing increase as expected. (link:https://issues.redhat.com/browse/OCPBUGS-42323[*OCPBUGS-42323*])
      Show
      * Previously, when the `globallyDisableIrqLoadBalancing` field was set to `true` in the `PerformanceProfile` object, the isolated CPUs were listed in the `IRQBALANCE_BANNED_CPULIST` variable instead of the `IRQBALANCE_BANNED_CPUS` variable. These variables are stored in `/etc/sysconfig/irqbalance`. Changing the value of the `globallyDisableIrqLoadBalancing` field from `true` to `false` did not update the `IRQBALANCE_BANNED_CPULIST` variable correctly. As a result, the number of CPUs available for load rebalancing did not increase because the isolated CPUs remained in the `IRQBALANCE_BANNED_CPULIST` variable. With this release, a fix ensures that isolated CPUs are now listed in the `IRQBALANCE_BANNED_CPUS` variable, so that the number of CPUs available for load rebalancing increase as expected. (link: https://issues.redhat.com/browse/OCPBUGS-42323 [* OCPBUGS-42323 *])
    • Bug Fix
    • Done

      Description of problem:

          when globallyDisableIrqLoadBalancing is set to true in Performance profile IRQBALANCE_BANNED_CPUS doesn't get updated with isolated cpus set in the profile instead IRQBALANCE_BANNED_CPULIST gets updated

      Version-Release number of selected component (if applicable):

      4.17.0-rc.5

      How reproducible:
      Everytime

      Steps to Reproduce:

          1. Setup performance profile as show below:

spec:
  cpu:
    isolated: 1,3-38,41,43-78
    reserved: 0,2,39,40,42,79
  globallyDisableIrqLoadBalancing: true
  hugepages:
    defaultHugepagesSize: 1G
    pages:
    - count: 1
      node: 0
      size: 1G
    - count: 128
      node: 1
      size: 2M
  machineConfigPoolSelector:
    machineconfiguration.openshift.io/role: worker-cnf
  net:
    userLevelNetworking: true
  nodeSelector:
    node-role.kubernetes.io/worker-cnf: ""
  numa:
    topologyPolicy: single-numa-node
  realTimeKernel:
    enabled: false
  workloadHints:
    highPowerConsumption: true
    perPodPowerManagement: false
    realTime: true

    2.  check /etc/sysconfig/irqbalance in the worker-cnf node:
IRQBALANCE_BANNED_CPUS=0
IRQBALANCE_BANNED_CPULIST=1,3-38,41,43-78

    3.

      Actual results:

      IRQBALANCE_BANNED_CPUS=0
IRQBALANCE_BANNED_CPULIST=1,3-38,41,43-78

      Expected results:

      IRQBALANCE_BANNED_CPUS=1,3-38,41,43-78

      Additional info:

              yquinn@redhat.com Yanir Quinn
              mniranja Mallapadi Niranjan
              Liquan Cui Liquan Cui
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: