aboutsummaryrefslogtreecommitdiff
path: root/Documentation/scheduler/sched-domains.rst
diff options
context:
space:
mode:
authorTang Yizhou2021-12-21 11:18:18 +0800
committerJonathan Corbet2022-02-01 16:29:25 -0700
commit5dbbc145d24ac68fc481fc6fe0e4ec3d7a4b8007 (patch)
tree837849aa741ffad4ffd3614cb8d297ee7fd53ecd /Documentation/scheduler/sched-domains.rst
parentdc6cdced47ce1edbca79bdc5a3cd4e435b5358dd (diff)
docs: scheduler: Fix outdated parameter of rebalance_domains
According to the function prototype of rebalance_domains(), its first parameter is *rq* and the document need to be updated. Signed-off-by: Tang Yizhou <tangyizhou@huawei.com> Link: https://lore.kernel.org/r/20211221031818.23186-1-tangyizhou@huawei.com Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/scheduler/sched-domains.rst')
-rw-r--r--Documentation/scheduler/sched-domains.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/scheduler/sched-domains.rst b/Documentation/scheduler/sched-domains.rst
index 84dcdcd2911c..e57ad28301bd 100644
--- a/Documentation/scheduler/sched-domains.rst
+++ b/Documentation/scheduler/sched-domains.rst
@@ -37,10 +37,10 @@ rebalancing event for the current runqueue has arrived. The actual load
balancing workhorse, run_rebalance_domains()->rebalance_domains(), is then run
in softirq context (SCHED_SOFTIRQ).
-The latter function takes two arguments: the current CPU and whether it was idle
-at the time the scheduler_tick() happened and iterates over all sched domains
-our CPU is on, starting from its base domain and going up the ->parent chain.
-While doing that, it checks to see if the current domain has exhausted its
+The latter function takes two arguments: the runqueue of current CPU and whether
+the CPU was idle at the time the scheduler_tick() happened and iterates over all
+sched domains our CPU is on, starting from its base domain and going up the ->parent
+chain. While doing that, it checks to see if the current domain has exhausted its
rebalance interval. If so, it runs load_balance() on that domain. It then checks
the parent sched_domain (if it exists), and the parent of the parent and so
forth.