Skip to content

[4.21] CNF-18941: perfprof: enable exec-cpu-affinity by default#1484

Open
shajmakh wants to merge 5 commits intoopenshift:release-4.21from
shajmakh:backport-execcpuaff-4.21
Open

[4.21] CNF-18941: perfprof: enable exec-cpu-affinity by default#1484
shajmakh wants to merge 5 commits intoopenshift:release-4.21from
shajmakh:backport-execcpuaff-4.21

Conversation

@shajmakh
Copy link
Contributor

@shajmakh shajmakh commented Mar 17, 2026

For High-performance configuration, cri-o started supporting exec-cpu-affinity feature and when configured to first it provides the ability for exec process to be pinned to the first CPU from the shared-CPUs IF set or to the first one from the islolated set.
(see cri-o/cri-o@4dd7fb9)

In performance profile, we want to enable this high-performance feature by default, and disable it (legacy) it provides an annotation option.

The annotation is there just as a backup in case of bugs getting reported by the consequences of this feature enablement, and should be removed in 3 releases.
manual backport of: #1426, #1432

For High-performance configuration, cri-o started supporting exec-cpu-affinity
feature and when configured to `first` it provides the ability for exec
process to be pinned to the first CPU from the shared-CPUs IF set
or to the first one from the islolated set.
(see cri-o/cri-o@4dd7fb9)

In performance profile, we want to enable this high-performance feature
by default, and disable it (legacy) it provides an annotation option.

The annotation is there just as a backup in case of bugs getting
reported by the consequences of this feature enablement, and should be
removed in 2 releases.

Run `./hack/render-sync.sh` to update the (no-cluster) e2e tests
expected outputs.

Signed-off-by: Shereen Haj <shajmakh@redhat.com>
(cherry picked from commit 370d4a3)
The annotation tells crun to manage container's cgroup using
 the systemd default subgroup behavior. This is meant to reduce
the nested cgroups so the container cgroup is placed on the pod/system
clice (the parent) rather than creating a cgroup per container.

Signed-off-by: Shereen Haj <shajmakh@redhat.com>
(cherry picked from commit 16d02b2)
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 17, 2026
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 17, 2026

@shajmakh: This pull request references CNF-18941 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target the "4.21.z" version, but no target version was set.

Details

In response to this:

For High-performance configuration, cri-o started supporting exec-cpu-affinity feature and when configured to first it provides the ability for exec process to be pinned to the first CPU from the shared-CPUs IF set or to the first one from the islolated set.
(see cri-o/cri-o@4dd7fb9)

In performance profile, we want to enable this high-performance feature by default, and disable it (legacy) it provides an annotation option.

The annotation is there just as a backup in case of bugs getting reported by the consequences of this feature enablement, and should be removed in 3 releases.

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 openshift-eng/jira-lifecycle-plugin repository.

@coderabbitai
Copy link

coderabbitai bot commented Mar 17, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8d145a38-a084-4373-97b7-003bce858418

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
📝 Coding Plan
  • Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Tip

You can make CodeRabbit's review stricter and more nitpicky using the `assertive` profile, if that's what you prefer.

Change the reviews.profile setting to assertive to make CodeRabbit's nitpick more issues in your PRs.

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 17, 2026

@shajmakh: This pull request references CNF-18941 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target the "4.21.z" version, but no target version was set.

Details

In response to this:

For High-performance configuration, cri-o started supporting exec-cpu-affinity feature and when configured to first it provides the ability for exec process to be pinned to the first CPU from the shared-CPUs IF set or to the first one from the islolated set.
(see cri-o/cri-o@4dd7fb9)

In performance profile, we want to enable this high-performance feature by default, and disable it (legacy) it provides an annotation option.

The annotation is there just as a backup in case of bugs getting reported by the consequences of this feature enablement, and should be removed in 3 releases.
manual backport of: #1426, #1432

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from Tal-or and swatisehgal March 17, 2026 18:49
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 17, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: shajmakh
Once this PR has been reviewed and has the lgtm label, please assign yanirq for approval. For more information see the Code Review Process.

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

Details 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

Introduce pods.DeleteAndSync helper (with client.Client parameter)
and replace all local deleteTestPod functions and inline
Get+Delete+WaitForDeletion patterns across functest suites
with calls to this shared utility.

Assisted-by: Cursor v2.3.37
AIA Attribution: AIA Primarily human, Stylistic edits, Human-initiated, Reviewed
Signed-off-by: Shereen Haj <shajmakh@redhat.com>
(cherry picked from commit d48bd52)
Add e2e tests to verify exec-cpu-affinity behavior across
cpu_management, updating_profile, and mixedcpus suites.
Tests verify that exec processes are pinned to the correct
exclusive, shared, or isolated CPU sets based on pod QoS class
and container resource requests.

Assisted-by: Cursor v2.3.37
AIA Attribution: AIA Primarily human, Stylistic edits, Human-initiated, Reviewed v1.0
Signed-off-by: Shereen Haj <shajmakh@redhat.com>
(cherry picked from commit 47d606470002f77e4e20ef3339a9fae196c26447)
Add unit tests for functions in resources helper package for tests.

Assisted-by: Cursor v1.2.2
AI-Attribution: AIA Entirely AI, Human-initiated, Reviewed, Cursor v1.2.2 v1.0

Signed-off-by: Shereen Haj <shajmakh@redhat.com>
(cherry picked from commit 3604b53)
@shajmakh shajmakh force-pushed the backport-execcpuaff-4.21 branch from 245775d to d3b885a Compare March 17, 2026 18:54
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 17, 2026

@shajmakh: 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/verify-deps d3b885a link true /test verify-deps
ci/prow/e2e-gcp-pao-workloadhints d3b885a link true /test e2e-gcp-pao-workloadhints
ci/prow/e2e-gcp-pao-updating-profile d3b885a link true /test e2e-gcp-pao-updating-profile
ci/prow/vet d3b885a link true /test vet
ci/prow/lint d3b885a link true /test lint

Full PR test history. Your PR dashboard.

Details

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants