Skip to content

Conversation

@MarSik
Copy link
Contributor

@MarSik MarSik commented Nov 26, 2024

Use the new IRQBALANCE_BANNED_CPULIST variable

The IRQBALANCE_BANNED_CPUS variable is deprecated and will not
be used anymore in the near future.

The newer IRQBALANCE_BANNED_CPULIST variable is already supported
by irqbalanced (https://github.com/Irqbalance/irqbalance/blob/v1.9.0/cputree.c#L135)
and should be used.

This must be merged together with cri-o/cri-o#8783

The IRQBALANCE_BANNED_CPUS variable is deprecated and will not
be used anymore in the near future.

The newer IRQBALANCE_BANNED_CPULIST variable is already supported
by irqbalanced (https://github.com/Irqbalance/irqbalance/blob/v1.9.0/cputree.c#L135)
and should be used.

This must be merged together with cri-o/cri-o#8783

Signed-off-by: Martin Sivak <[email protected]>
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 26, 2024
@openshift-ci openshift-ci bot requested review from dagrayvid and ffromani November 26, 2024 13:30
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 26, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: MarSik

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 26, 2024
@jmencak
Copy link
Contributor

jmencak commented Nov 26, 2024

/cc jmencak

@openshift-ci openshift-ci bot requested a review from jmencak November 26, 2024 13:41
Copy link
Contributor

@jmencak jmencak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • missing "make render-sync"
  • Unit tests are failing with this, they'll likely need to be adjusted.


# CPU numbers which have their corresponding bits set to one in this mask
# will not have any irq's assigned to them on rebalance.
# so zero means all cpus are participating in load balancing.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment needs to be adjusted, there's no longer 0. We have empty string.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In fact, we will need to change it to a "-", because an empty string inherits from nohz_full.

Copy link
Contributor

@Tal-or Tal-or left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what should go first? this one or cri-o/cri-o#8931

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 17, 2025

@MarSik: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-gcp-pao-updating-profile d8acd3a link true /test e2e-gcp-pao-updating-profile
ci/prow/e2e-gcp-pao d8acd3a link true /test e2e-gcp-pao
ci/prow/e2e-gcp-pao-workloadhints d8acd3a link true /test e2e-gcp-pao-workloadhints
ci/prow/e2e-no-cluster d8acd3a link true /test e2e-no-cluster
ci/prow/e2e-hypershift-pao d8acd3a link true /test e2e-hypershift-pao
ci/prow/unit d8acd3a link true /test unit

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.

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 16, 2025
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 16, 2025
@MarSik
Copy link
Contributor Author

MarSik commented Aug 7, 2025

/remove-lifecycle rotten

@openshift-ci openshift-ci bot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Aug 7, 2025
@MarSik
Copy link
Contributor Author

MarSik commented Aug 7, 2025

/hold waiting for cri-o/cri-o#8931

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 7, 2025
@Tal-or
Copy link
Contributor

Tal-or commented Aug 11, 2025

@MarSik See: #1350

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 10, 2025
@Tal-or
Copy link
Contributor

Tal-or commented Nov 11, 2025

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants