Pull scheduler updates from Thomas Gleixner: - migrate_disable/enable() support which originates from the RT tree and is now a prerequisite for the new preemptible kmap_local() API which aims to replace kmap_atomic(). - A fair amount of topology and NUMA related improvements - Improvements for the frequency invariant calculations - Enhanced robustness for the global CPU priority tracking and decision making - The usual small fixes and enhancements all over the place * tag 'sched-core-2020-12-14' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: (61 commits) sched/fair: Trivial correction of the newidle_balance() comment sched/fair: Clear SMT siblings after determining the core is not idle sched: Fix kernel-doc markup x86: Print ratio freq_max/freq_base used in frequency invariance calculations x86, sched: Use midpoint of max_boost and max_P for frequency invariance on AMD EPYC x86, sched: Calculate frequency invariance for AMD systems irq_work: Optimize irq_work_single() smp: Cleanup smp_call_function*() irq_work: Cleanup sched: Limit the amount of NUMA imbalance that can exist at fork time sched/numa: Allow a floating imbalance between NUMA nodes sched: Avoid unnecessary calculation of load imbalance at clone time sched/numa: Rename nr_running and break out the magic number sched: Make migrate_disable/enable() independent of RT sched/topology: Condition EAS enablement on FIE support arm64: Rebuild sched domains on invariance status changes sched/topology,schedutil: Wrap sched domains rebuild sched/uclamp: Allow to reset a task uclamp constraint value sched/core: Fix typos in comments Documentation: scheduler: fix information on arch SD flags, sched_domain and sched_debug ...
Showing the changes to include/uapi/linux (1 of 59 files). Show all
Unified · Split
| @@ -96,6 +96,8 @@ struct sched_param { · 95 unmodified lines | |||
| 96 | * on a CPU with a capacity big enough to fit the specified value. | 96 | * on a CPU with a capacity big enough to fit the specified value. |
| 97 | * A task with a max utilization value smaller than 1024 is more likely | 97 | * A task with a max utilization value smaller than 1024 is more likely |
| 98 | * scheduled on a CPU with no more capacity than the specified value. | 98 | * scheduled on a CPU with no more capacity than the specified value. |
| 99 | * | ||
| 100 | * A task utilization boundary can be reset by setting the attribute to -1. | ||
| 99 | */ | 101 | */ |
| 100 | struct sched_attr { | 102 | struct sched_attr { |
| 101 | __u32 size; | 103 | __u32 size; |