scx_bpfland: Rethink per-CPU tasks prioritization #2987
                
     Merged
            
            
          
  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.
  
    
  
    
Now that we always pick the task with the earliest deadline between the per-node DSQ and per-CPU DSQ, see commit 9cb2779 ("scx_bpfland: Avoid starvation in per-node DSQs"), we can always dispatch per-CPU tasks to the corresponding per-CPU DSQ and reduce the locking pressure on the per-node DSQs, without regressing system responsiveness.
Moreover, change per-CPU tasks prioritization (option --local-pcpu / -p) to always dispatch per-CPU tasks to the local DSQ (SCX_DSQ_LOCAL). With this option enabled, strictly affinitized tasks may still starve non-affinitized ones (as before), but they also receive a higher priority, which can be beneficial for certain workloads.