[mpmd] Integrate PipelineSchedule API into jit lowering flow #798
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
copybara-service
bot
force-pushed
the
test_808549034
branch
from
4ac03e9 to
12cbe5c
Compare
copybara-service
bot
changed the title
copybara-service
bot
force-pushed
the
test_808549034
branch
2 times, most recently
from
d9214ad to
3eb4859
Compare
copybara-service
bot
force-pushed
the
test_808549034
branch
6 times, most recently
from
e0e5eac to
0e7d8e5
Compare
copybara-service
bot
force-pushed
the
test_808549034
branch
from
0e7d8e5 to
0ce3f30
Compare
copybara-service
bot
changed the title
copybara-service
bot
force-pushed
the
test_808549034
branch
4 times, most recently
from
931260b to
4f53d94
Compare
copybara-service
bot
force-pushed
the
test_808549034
branch
3 times, most recently
from
7bca49a to
8e81972
Compare
Lowering Flow: When a `PipelineSchedule` is provided in `MpmdConfig`, the `mpmd.jit` lowering process first runs the IMPORT pass only to generate initial fragments. The rule builders defined within the `PipelineSchedule` are then invoked to generate scheduling and merging rules based on these fragments. These rules are used during the subsequent passes, specifically OPTIMIZE. User defined partitioning options are checked to ensure they don't conflict with options required by `PipelineSchedule`. This new API replaces the direct usage of `fragment_merge_rules` and `fragment_schedule_rules` in `MpmdConfig`. PiperOrigin-RevId: 808549034
copybara-service
bot
force-pushed
the
test_808549034
branch
from
8e81972 to
a4782f9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
[mpmd] Integrate PipelineSchedule API into jit lowering flow
Lowering Flow:
When a
PipelineScheduleis provided inMpmdConfig, thempmd.jitloweringprocess first runs the IMPORT pass only to generate initial fragments. The rule
builders defined within the
PipelineScheduleare then invoked to generatescheduling and merging rules based on these fragments. These rules are used
during the subsequent passes, specifically OPTIMIZE. User defined partitioning
options are checked to ensure they don't conflict with options required by
PipelineSchedule.This new API replaces the direct usage of
fragment_merge_rulesandfragment_schedule_rulesinMpmdConfig.