Skip to content

Conversation

@alan-maguire
Copy link
Member

fixes around non-global network namespaces and sysctl-based disable when external entity changes a sysctl we manage. prior to these fixes we were disabling non-global ns when the global ns was switched off; these changes ensure non-global ns can still work when global has been disabled. also add the name of the process that triggered the disable for better diagnosis.

when we change a sysctl external to bpftune, the aim is to disable the
auto-tuning for the associated namespace. however in the global ns
we were disabling tuning for global and non-global namespaces via
bpftuner_fini().  Ensure we disable global namespace only, and that we
only send events for tuners that are enabled and - if namespaced -
if the namespace is enabled also.

Reported by: Roger Knobbe (https://github.com/rknobbe)
Signed-off-by: Alan Maguire <[email protected]>
this will help diagnose the cause of sysctl changes that disable
auto-tuning.

Signed-off-by: Alan Maguire <[email protected]>
@oracle-contributor-agreement oracle-contributor-agreement bot added the OCA Verified All contributors have signed the Oracle Contributor Agreement. label Nov 26, 2024
@alan-maguire alan-maguire merged commit b903c88 into main Nov 26, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

OCA Verified All contributors have signed the Oracle Contributor Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant