Preemption refactor #188
Merged
Preemption refactor #188
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MatteoNardi
force-pushed
the
preemption_refactor
branch
from
540f45e to
f12c1d4
Compare
MatteoNardi
force-pushed
the
preemption_refactor
branch
from
e30980c to
967551b
Compare
MatteoNardi
changed the base branch from
148-explore-possibilities-of-bpf_loop
to
main
banditopazzo
requested changes
Jun 26, 2023
banditopazzo
approved these changes
Jun 27, 2023
MatteoNardi
force-pushed
the
preemption_refactor
branch
from
f78c2ce to
1ca8574
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
eBPF programs could interrupt each other, see "Are BPF programs preemptible?" thread on the kernel BPF mailing list:
https://lore.kernel.org/bpf/878rhty100.fsf@cloudflare.com/T/#t