GPU Task Scheduling With Deadline-Aware Context Switching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional GPU scheduling methods lead to inefficient context switching due to the depth of pipelines and large caches, resulting in high costs in terms of efficiency and memory bandwidth, and do not effectively manage power consumption and heat generation.

Innovation Solution

Implementing a method that estimates the completion times of GPU tasks and compares them to deadlines to determine if context switching is necessary, allowing lower priority tasks to continue if both can be completed before the deadline, and adjusting the operating point of the GPU using dynamic voltage and frequency scaling (DVFS) to meet task deadlines.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If context switching is performed based on priority in conventional GPU scheduling, then higher priority tasks can be executed promptly, but the depth of pipelines and large caches cause inefficient context switching with high costs in efficiency and memory bandwidth

Engineering Contradiction:
Improvetask execution speedVSAvoidGPU efficiency
Core Design Contradiction:
SpeedVSProductivity

Solution Approach 1:

The patent applies preliminary action by estimating the completion time of the currently executing task before making a context switching decision. The scheduler predicts how long the current task will take to finish, and based on this prediction and the deadline of the higher priority task, decides in advance whether to switch contexts. This prevents unnecessary context switches and their associated overhead, thereby maintaining GPU efficiency while still allowing timely execution of high-priority tasks when needed.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If context switching is enabled for higher priority tasks, then task priority management is improved, but the number of context switches increases leading to higher power consumption and heat generation

Engineering Contradiction:
Improvepriority management flexibilityVSAvoidpower consumption
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent implements feedback by continuously monitoring task completion times and using this information to refine future estimates. The scheduler learns from actual execution patterns and adjusts its predictions accordingly, enabling more accurate decisions about when context switching is truly necessary. This feedback mechanism reduces unnecessary context switches and their associated power consumption while maintaining effective priority management.

Inventive Principle:
Principle #23Feedback

3Ease of operation

If conventional scheduling methods are used, then simple priority-based execution is achieved, but they do not effectively manage power consumption and heat generation

Engineering Contradiction:
Improvescheduling simplicityVSAvoidheat generation
Core Design Contradiction:
Ease of operationVSTemperature

Solution Approach 1:

The patent applies parameter changes by dynamically adjusting the scheduling decision based on the estimated completion time parameter. Instead of using a fixed priority-based scheduling rule, the system modifies its behavior based on the predicted duration of the current task and the deadline of the higher priority task. This parameter-driven approach maintains scheduling simplicity while reducing unnecessary context switches and their associated heat generation.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12596573B2Controlling scheduling of a GPU
Publication Date: 2026.04.07 IMAGINATION TECH LTD
  • US12596573B2 patent drawing
  • US12596573B2 patent drawing
  • US12596573B2 patent drawing

AI summary

The operation of a GPU is controlled based on one or more deadlines by which one or more GPU tasks must be completed and estimates of the time required to complete the execution of a first GPU task (which is currently being executed) and the time required to execute one or more other GPU tasks (which are not currently being executed). Based on a comparison between the deadline(s) and the estimates, context switching may or may not be triggered.