Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refresh after attach #150

Merged
merged 2 commits into from
Feb 22, 2024
Merged

Refresh after attach #150

merged 2 commits into from
Feb 22, 2024

Conversation

Byte-Lab
Copy link
Contributor

For some reason we're sometimes (non-deterministically) not seeing the
updated cpumask / layer values in BPF if we initialize the cpumasks here
before attaching. Let's undo this for now so to avoid observing buggy
behavior, until we figure it out.

This reverts commit 56ff343.

For some reason we seem to be non-deterministically failing to see the
updated layer values in BPF if we initialize before attaching. Let's
just undo this specific part so that we can unblock this being broken,
and we can figure it out async.

Signed-off-by: David Vernet <void@manifault.com>
As mentioned in the previous commit, for some reason we're sometimes
(non-deterministically) not seeing the updated cpumask / layer values in
BPF if we initialize the cpumasks here before attaching. Let's undo this
for now so to avoid observing buggy behavior, until we figure it out.

Signed-off-by: David Vernet <void@manifault.com>
@Byte-Lab Byte-Lab requested a review from htejun February 22, 2024 01:21
@htejun htejun merged commit b77996f into main Feb 22, 2024
1 check passed
@Byte-Lab Byte-Lab deleted the refresh_after_attach branch March 14, 2024 18:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants