- 
                Notifications
    
You must be signed in to change notification settings  - Fork 68
 
[DO NOT REVIEW] Remove ParallelExtentMap and use ParallelDimensionMap everywhere instead #5446
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
base: main
Are you sure you want to change the base?
Conversation
| 
           !test --diff  | 
    
| 
          
 Review updated until commit 2923cb6 Description
 Changes walkthrough 📝
 PR Reviewer Guide 🔍Here are some key observations to aid the review process: 
  | 
    
| 
           !test --diff  | 
    
| 
           !test --diff  | 
    
| 
           !test --diff  | 
    
Prior to this change we have two separate systems for computing parallel extents:
ParallelDimensionMapis used to compute dimensions for generating the CUDA kernelKernelExecutoruses another system includingParallelExtentMapwhich gathers all of the extents of IDs in the promoted group for each paralleltype, and computes the max extent across all those.This is redundant: we should have a centralized place to find the following information:
In the future, we might include other stuff like predication for warp specialization. This PR is a step toward centralizing our parallel dimension mapping into
ParallelDimensionMapby removing the redundant parts inKernelExecutor.