script: add IRQBALANCE_BANNED_CPULIST variable #1420
Conversation
new version of irqbalance start using IRQBALANCE_BANNED_CPULIST to mark the banned CPUs that are not suppose to participate in the irq balancing. We're setting the new variable with a default value `-` which means that all CPUs are participating in the irq balancing. Signed-off-by: Talor Itzhak <titzhak@redhat.com>
This is only needed for cases when more control is required on the restore flow. cri-o/cri-o@e158549 In our case we do not need the restore flow at all, because the default behavior of the dynamic irqbalancing provided by cri-o is good enough for us. hence, we disable the restore flow completely. Signed-off-by: Talor Itzhak <titzhak@redhat.com>
Signed-off-by: Talor Itzhak <titzhak@redhat.com>
Signed-off-by: Talor Itzhak <titzhak@redhat.com>
|
/hold depends on cri-o/cri-o#8931 Closed by mistake |
openshift-ci
bot
added
the
do-not-merge/hold
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Tal-or The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
same as #1350 which was closed by mistake |
|
@Tal-or: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
1 participant
A new version of irqbalance start using IRQBALANCE_BANNED_CPULIST to mark the banned CPUs
that are not suppose to participate in the irq balancing.
We're setting the new variable with a default value - which
means that all CPUs are participating in the irq balancing.
Signed-off-by: Talor Itzhak titzhak@redhat.com