Mitosis Flag Burndown - #3684
Draft
tommy-u wants to merge 9 commits into
Draft
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
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.
Heads up, I worked on the plans for each, but these are robot changes. They aren't thoroughly tested or some kind of final code I'm necessarily trying to land in this form.
I'm sharing this as a draft to discuss how we want to go about burning down our flags by making them the default behavior in the scheduler.
I did these in ascending order of complexity:
As an afterthought I also removed:
Misc:
Notes:
I think we want to keep --exiting-task-workaround and --use-lockless-peek until we're certain about kernel fixes.
Some of the commits at the end should be moved to separate cleanup branches.