Messages in this thread Patch in this message | | | From | Bhaskar Chowdhury <> | Subject | [PATCH] sched/psi.c: Rudimentary typo fixes | Date | Fri, 26 Mar 2021 18:12:33 +0530 |
| |
s/possible/possible/ s/ exceution/execution/ s/manupulations/manipulations/
Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com> --- kernel/sched/psi.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/kernel/sched/psi.c b/kernel/sched/psi.c index 967732c0766c..316ebc57a115 100644 --- a/kernel/sched/psi.c +++ b/kernel/sched/psi.c @@ -59,7 +59,7 @@ * states, we would have to conclude a CPU SOME pressure number of * 100%, since *somebody* is waiting on a runqueue at all * times. However, that is clearly not the amount of contention the - * workload is experiencing: only one out of 256 possible exceution + * workload is experiencing: only one out of 256 possible execution * threads will be contended at any given time, or about 0.4%. * * Conversely, consider a scenario of 4 tasks and 4 CPUs where at any @@ -73,7 +73,7 @@ * we have to base our calculation on the number of non-idle tasks in * conjunction with the number of available CPUs, which is the number * of potential execution threads. SOME becomes then the proportion of - * delayed tasks to possibe threads, and FULL is the share of possible + * delayed tasks to possible threads, and FULL is the share of possible * threads that are unproductive due to delays: * * threads = min(nr_nonidle_tasks, nr_cpus) @@ -441,7 +441,7 @@ static void psi_avgs_work(struct work_struct *work) mutex_unlock(&group->avgs_lock); }
-/* Trigger tracking window manupulations */ +/* Trigger tracking window manipulations */ static void window_reset(struct psi_window *win, u64 now, u64 value, u64 prev_growth) { -- 2.26.2
| |