From: "tip-bot2 for Bharata B Rao" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Bharata B Rao <bharata@amd.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Mel Gorman <mgorman@suse.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: sched/core] sched/numa: Fix a few comments
Date: Thu, 14 Oct 2021 11:16:19 -0000 [thread overview]
Message-ID: <163421017992.25758.2626208384412078593.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20211004105706.3669-4-bharata@amd.com>
The following commit has been merged into the sched/core branch of tip:
Commit-ID: 7d380f24fe662033fd21a65f678057abd293f76e
Gitweb: https://git.kernel.org/tip/7d380f24fe662033fd21a65f678057abd293f76e
Author: Bharata B Rao <bharata@amd.com>
AuthorDate: Mon, 04 Oct 2021 16:27:05 +05:30
Committer: Peter Zijlstra <peterz@infradead.org>
CommitterDate: Thu, 14 Oct 2021 13:09:58 +02:00
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
---
kernel/sched/fair.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index cfbd5ef..87db481 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
next prev parent reply other threads:[~2021-10-14 11:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 10:57 [PATCH 0/4] A few autonuma cleanups Bharata B Rao
2021-10-04 10:57 ` [PATCH 1/4] sched/numa: Replace hard-coded number by a define in numa_task_group() Bharata B Rao
2021-10-05 8:18 ` Mel Gorman
2021-10-09 10:07 ` [tip: sched/core] " tip-bot2 for Bharata B Rao
2021-10-14 11:16 ` tip-bot2 for Bharata B Rao
2021-10-04 10:57 ` [PATCH 2/4] sched/numa: Remove the redundant member numa_group::fault_cpus Bharata B Rao
2021-10-05 8:21 ` Mel Gorman
2021-10-09 10:07 ` [tip: sched/core] " tip-bot2 for Bharata B Rao
2021-10-14 11:16 ` tip-bot2 for Bharata B Rao
2021-10-04 10:57 ` [PATCH 3/4] sched/numa: Fix a few comments Bharata B Rao
2021-10-05 8:22 ` Mel Gorman
2021-10-09 10:07 ` [tip: sched/core] " tip-bot2 for Bharata B Rao
2021-10-14 11:16 ` tip-bot2 for Bharata B Rao [this message]
2021-10-04 10:57 ` [RFC PATCH 4/4] sched/numa: Don't update mm->numa_next_scan from fault path Bharata B Rao
2021-10-05 8:23 ` Mel Gorman
2021-10-05 9:10 ` Bharata B Rao
2021-10-07 10:25 ` Mel Gorman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=163421017992.25758.2626208384412078593.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=bharata@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=peterz@infradead.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®