[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <tip-9c2298aad355d8c1957df3015448fef333526934@git.kernel.org>
Date: Thu, 4 Oct 2018 03:04:45 -0700
From: "tip-bot for Rafael J. Wysocki" <tipbot@...or.com>
To: linux-tip-commits@...r.kernel.org
Cc: rafael.j.wysocki@...el.com, tj@...nel.org,
linux-pm@...r.kernel.org, torvalds@...ux-foundation.org,
hpa@...or.com, linux-kernel@...r.kernel.org, tglx@...utronix.de,
peterz@...radead.org, mingo@...nel.org
Subject: [tip:sched/core] sched/core: Fix comment regarding nr_iowait_cpu()
and get_iowait_load()
Commit-ID: 9c2298aad355d8c1957df3015448fef333526934
Gitweb: https://git.kernel.org/tip/9c2298aad355d8c1957df3015448fef333526934
Author: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
AuthorDate: Thu, 4 Oct 2018 11:05:14 +0200
Committer: Ingo Molnar <mingo@...nel.org>
CommitDate: Thu, 4 Oct 2018 11:25:56 +0200
sched/core: Fix comment regarding nr_iowait_cpu() and get_iowait_load()
The comment related to nr_iowait_cpu() and get_iowait_load() confuses
cpufreq with cpuidle and is not very useful for this reason, so fix it.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
Acked-by: Peter Zijlstra <peterz@...radead.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Linux PM <linux-pm@...r.kernel.org>
Cc: Tejun Heo <tj@...nel.org>
Cc: Thomas Gleixner <tglx@...utronix.de>
Fixes: e33a9bba85a8 "sched/core: move IO scheduling accounting from io_schedule_timeout() into scheduler"
Link: http://lkml.kernel.org/r/3803514.xkx7zY50tF@aspire.rjw.lan
Signed-off-by: Ingo Molnar <mingo@...nel.org>
---
kernel/sched/core.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 56b3c1781276..fe0223121883 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -2916,10 +2916,10 @@ unsigned long nr_iowait(void)
}
/*
- * Consumers of these two interfaces, like for example the cpufreq menu
- * governor are using nonsensical data. Boosting frequency for a CPU that has
- * IO-wait which might not even end up running the task when it does become
- * runnable.
+ * Consumers of these two interfaces, like for example the cpuidle menu
+ * governor, are using nonsensical data. Preferring shallow idle state selection
+ * for a CPU that has IO-wait which might not even end up running the task when
+ * it does become runnable.
*/
unsigned long nr_iowait_cpu(int cpu)
Powered by blists - more mailing lists