Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@pperiyasamy
Copy link
Member

@pperiyasamy pperiyasamy commented Dec 17, 2020

This would manipulate irqbalance service if it's already running on the system to exclude assigned pod CPUs from IRQ balancing.

Signed-off-by: Periyasamy Palanisamy [email protected]

What type of PR is this?

/kind api-change
/kind bug
/kind ci
/kind cleanup
/kind dependency-change
/kind deprecation
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake
/kind other

What this PR does / why we need it:

The crio currently runs irqbalance --oneshot command to exclude pod cpus from handling interrupts, but this may not be a right choice if irqbalance service is already running on the system. This PR aims to address that concern by restarting the service after updating irqbalance config file with required settings for IRQBALANCE_BANNED_CPUS parameter.

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

This change is not yet tested, after a initial round of reviews would go for testing out this change.

Does this PR introduce a user-facing change?

When using high performance hooks, CRI-O now restarts the irqbalance service after updating the irqbalance config file. rather than calling `irqbalance --oneshot`. A new config value `irqbalance_config_file` has been introduced to configure the file to update with `IRQBALANCE_BANNED_CPUS` settings. The default of this config value is `/etc/sysconfig/irqbalance`, but must be set to `/etc/default/irqbalance` for Ubuntu-like distributions.

@openshift-ci-robot openshift-ci-robot added the dco-signoff: yes Indicates the PR's author has DCO signed all their commits. label Dec 17, 2020
@openshift-ci-robot openshift-ci-robot added the do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. label Dec 17, 2020
@openshift-ci-robot
Copy link

Hi @pperiyasamy. Thanks for your PR.

I'm waiting for a cri-o member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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/test-infra repository.

@openshift-ci-robot openshift-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Dec 17, 2020
@pperiyasamy
Copy link
Member Author

pperiyasamy commented Dec 17, 2020

/cc @JanScheurich

@TomSweeneyRedHat
Copy link
Contributor

@pperiyasamy looks like you've some lint issues.

@TomSweeneyRedHat
Copy link
Contributor

Any tests to add or at least to modify?

@pperiyasamy
Copy link
Member Author

pperiyasamy commented Dec 17, 2020

@TomSweeneyRedHat Thanks, golint issues are fixed now, I'm waiting for the initial feedback on the changes, if that is finalised, then I'm planning to test this on my local setup and add/modify test cases.

@haircommander
Copy link
Member

@jianzzha @cynepco3hahue PTAL

// HighPerformanceHooks used to run additional hooks that will configure a system for the latency sensitive workloads
type HighPerformanceHooks struct{}
type HighPerformanceHooks struct {
irqBalanceConfigFile string
Copy link
Member

Choose a reason for hiding this comment

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

why have this file as a member of the Hooks, when the other file locations are hardcoded?

Copy link
Member Author

Choose a reason for hiding this comment

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

@haircommander This file location is platform dependent. For example, in Ubuntu, the config file is /etc/default/irqbalance. Hence making it to configure from a RuntimeConfig property. Can you check it now ?

@codecov
Copy link

codecov bot commented Dec 17, 2020

Codecov Report

Merging #4441 (77f1b7c) into master (3a90a17) will increase coverage by 0.06%.
The diff coverage is 45.19%.

@@            Coverage Diff             @@
##           master    #4441      +/-   ##
==========================================
+ Coverage   40.03%   40.10%   +0.06%     
==========================================
  Files         116      116              
  Lines        9391     9481      +90     
==========================================
+ Hits         3760     3802      +42     
- Misses       5224     5256      +32     
- Partials      407      423      +16     

@pperiyasamy pperiyasamy force-pushed the irq branch 2 times, most recently from 856b7f0 to b98fea6 Compare January 5, 2021 12:35
@jianzzha
Copy link
Contributor

jianzzha commented Jan 5, 2021

@jianzzha @cynepco3hahue PTAL

@haircommander I will get someone to validate this in centos

@haircommander
Copy link
Member

/ok-to-test

@openshift-ci-robot openshift-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jan 5, 2021
@haircommander
Copy link
Member

by the way, thanks for taking this on @pperiyasamy, and thanks @jianzzha for the testing help !

lines := strings.Split(string(input), "\n")
found := false
for i, line := range lines {
if strings.Contains(line, irqBalanceBannedCpus+"=") {
Copy link
Contributor

Choose a reason for hiding this comment

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

make sure this is a true config line, not in a comment line, e.g. no leading non-space characters

Copy link
Member Author

Choose a reason for hiding this comment

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

correct, now changed to use HasPrefix method, i guess that should be ok.

logrus.Warnf("irqbalance binary not found: %v", err)
return nil

if !fileExists(irqBalanceConfigFile) {
Copy link
Contributor

Choose a reason for hiding this comment

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

can we think of a better way to test if irqbalance service is enabled rather than test the config file existence? I mean it is possible that the service config file exists but the service is disabled. The original idea was that the irqbalance service was disabled via external mechanism outside crio or k8s, for example via deployment orchestration. Not sure if any deployment has taken that route but it is always a good idea to be careful.

Copy link
Member Author

Choose a reason for hiding this comment

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

yes, good point! added is-enabled check now.

}

// RestoreIrqBalanceConfig restores irqbalance service with original banned cpu mask settings
func RestoreIrqBalanceConfig(irqBalanceConfigFile, irqBannedCPUConfigFile string) error {
Copy link
Contributor

Choose a reason for hiding this comment

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

Thanks for adding this restore function. Can we check if the irqbalance service is enabled before restart it?

Copy link
Member Author

Choose a reason for hiding this comment

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

sure, done.

Copy link
Contributor

Choose a reason for hiding this comment

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

looks good to me

@jianzzha
Copy link
Contributor

jianzzha commented Jan 7, 2021

@haircommander integration test on bare metal (centos k8s) works fine; some minor comments posted inline
@cynepco3hahue on the openshift side - I see no extra work to adopt this
@pperiyasamy can you take a look of the inline comments

**apparmor_profile**=""
Used to change the name of the default AppArmor profile of CRI-O. The default profile name is "crio-default".

**irqbalance_config_file**="/etc/sysconfig/irqbalance"
Copy link
Member

Choose a reason for hiding this comment

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

can you add a blurb about where this file should be for which distro (only for the most popular: ubuntu/centos, maybe debian/rhel if they differ at all)

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes! done, I was able to confirm the file locations only in centos/suse and ubuntu platforms. so added it only for those cases.

@pperiyasamy
Copy link
Member Author

pperiyasamy commented Jan 7, 2021

@pperiyasamy: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/openshift-jenkins/integration_crun e14e386 link /test integration_crun
ci/prow/e2e-gcp e14e386 link /test e2e-gcp
ci/prow/e2e-agnostic e14e386 link /test e2e-agnostic
Full PR test history. Your PR dashboard.

@haircommander thanks, while addressing your review comments, any idea while these checks are failing ? Looks it's not related to this PR.

@haircommander
Copy link
Member

the ci/prow/e2e* are generally flaky and I believe integration_crun was a provisioning flake
/retest

jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Nov 22, 2022
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file to empty string ("").

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Nov 24, 2022
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file to empty string ("").

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Dec 1, 2022
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file to empty string ("").

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Dec 1, 2022
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file to empty string ("").

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Dec 9, 2022
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file to empty string ("").

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Dec 12, 2022
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file to empty string ("").

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Dec 12, 2022
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file to empty string ("").

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Dec 13, 2022
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file to empty string ("").

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Dec 14, 2022
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file to empty string ("").

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Dec 15, 2022
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file to empty string ("").

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Dec 16, 2022
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file to empty string ("").

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Dec 16, 2022
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file "disable".

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Dec 16, 2022
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file "disable".

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Dec 19, 2022
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file "disable".

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Dec 20, 2022
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file "disable".

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Dec 21, 2022
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file "disable".

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Dec 22, 2022
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file "disable".

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Jan 2, 2023
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file "disable".

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Jan 10, 2023
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file "disable".

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Jan 16, 2023
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file "disable".

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Jan 20, 2023
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file "disable".

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Jan 24, 2023
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file "disable".

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Jan 25, 2023
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file "disable".

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Jan 25, 2023
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file "disable".

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Jan 25, 2023
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file "disable".

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Feb 3, 2023
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file "disable".

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Feb 10, 2023
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file "disable".

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Feb 22, 2023
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file "disable".

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
jlojosnegros pushed a commit to jlojosnegros/cri-o that referenced this pull request Feb 23, 2023
Since cri-o#4441 , to support
the dynamic irqbalance configuration in turn needed by the high
performance hooks, CRI-O runs the restore code at startup.

In some configuration scenarios it's preferred to have
more control over this step. Some configuration wants
to have more control over the mask to be restored, or to
disable the restore flow entirely.

For this reason, we add an option to provide a user-supplied
restore file. Users wishing to exert more control can provide
their data, or they can disable the flow entirely setting
the path to the restore file "disable".

The new option defaults are meant to ensure full backward
compatibility.

Signed-off-by: Francesco Romani <[email protected]>
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. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note Denotes a PR that will be considered when it comes time to generate release notes.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants