Sharing information between scheduler and frameworks
Registered by
Vincent Guittot
This topic is scheduled with "How to improve the selection of the target cpu in the timer and workqueue framework":
https:/
The scheduler could take advantage of information from other frameworks, when it selects run queue for a task. These information are helpful not only for power consumption but also for performance by giving a mask of preferred CPUs. As an example, the wake up latency of a task is impacted by the C-states of the selected CPU. Choosing a CPU with a low C-state will reduce this latency.
This talk will discuss the various inputs that could be shared with the scheduler
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Vincent Guittot
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
(?)