summaryrefslogtreecommitdiff
path: root/kernel/sched
diff options
context:
space:
mode:
authorBharata B Rao <bharata@amd.com>2021-10-04 16:27:05 +0530
committerPeter Zijlstra <peterz@infradead.org>2021-10-14 13:09:58 +0200
commit7d380f24fe662033fd21a65f678057abd293f76e (patch)
tree32ba3f9a2ee43da8aae5c05517dda96098d80aa7 /kernel/sched
parent5b763a14a5164e4c442e99d186fb39dac489e49b (diff)
downloadlwn-7d380f24fe662033fd21a65f678057abd293f76e.tar.gz
lwn-7d380f24fe662033fd21a65f678057abd293f76e.zip
sched/numa: Fix a few comments
Fix a few comments to help understand them better. Signed-off-by: Bharata B Rao <bharata@amd.com> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Acked-by: Mel Gorman <mgorman@suse.de> Link: https://lkml.kernel.org/r/20211004105706.3669-4-bharata@amd.com
Diffstat (limited to 'kernel/sched')
-rw-r--r--kernel/sched/fair.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index cfbd5ef0b558..87db481e8a56 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -2074,7 +2074,7 @@ static void numa_migrate_preferred(struct task_struct *p)
}
/*
- * Find out how many nodes on the workload is actively running on. Do this by
+ * Find out how many nodes the workload is actively running on. Do this by
* tracking the nodes from which NUMA hinting faults are triggered. This can
* be different from the set of nodes where the workload's memory is currently
* located.
@@ -2128,7 +2128,7 @@ static void update_task_scan_period(struct task_struct *p,
/*
* If there were no record hinting faults then either the task is
- * completely idle or all activity is areas that are not of interest
+ * completely idle or all activity is in areas that are not of interest
* to automatic numa balancing. Related to that, if there were failed
* migration then it implies we are migrating too quickly or the local
* node is overloaded. In either case, scan slower