mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "tip-bot2 for Colin Ian King" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Colin Ian King <colin.i.king@gmail.com>,
	Ingo Molnar <mingo@kernel.org>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: sched/core] sched/headers: Remove comment referring to rq::cpu_load, since this has been removed
Date: Tue, 10 Oct 2023 21:47:53 -0000	[thread overview]
Message-ID: <169697447356.3135.18063293604947285416.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20231010155744.1381065-1-colin.i.king@gmail.com>

The following commit has been merged into the sched/core branch of tip:

Commit-ID:     b19fdb16fb2167c6bc9ee8fbc0c1d2d4fd3e2eb8
Gitweb:        https://git.kernel.org/tip/b19fdb16fb2167c6bc9ee8fbc0c1d2d4fd3e2eb8
Author:        Colin Ian King <colin.i.king@gmail.com>
AuthorDate:    Tue, 10 Oct 2023 16:57:44 +01:00
Committer:     Ingo Molnar <mingo@kernel.org>
CommitterDate: Tue, 10 Oct 2023 23:42:20 +02:00

sched/headers: Remove comment referring to rq::cpu_load, since this has been removed

There is a comment that refers to cpu_load, however, this cpu_load was
removed with:

  55627e3cd22c ("sched/core: Remove rq->cpu_load[]")

... back in 2019. The comment does not make sense with respect to this
removed array, so remove the comment.

Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Link: https://lore.kernel.org/r/20231010155744.1381065-1-colin.i.king@gmail.com
---
 kernel/sched/sched.h | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h
index faf9031..65cad0e 100644
--- a/kernel/sched/sched.h
+++ b/kernel/sched/sched.h
@@ -948,10 +948,6 @@ struct rq {
 	/* runqueue lock: */
 	raw_spinlock_t		__lock;
 
-	/*
-	 * nr_running and cpu_load should be in the same cacheline because
-	 * remote CPUs use both these fields when doing load calculation.
-	 */
 	unsigned int		nr_running;
 #ifdef CONFIG_NUMA_BALANCING
 	unsigned int		nr_numa_running;

      parent reply	other threads:[~2023-10-10 21:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10 15:57 [PATCH][next] sched/headers: remove comment referring to cpu_load " Colin Ian King
2023-10-10 21:32 ` [tip: sched/core] sched/headers: Remove comment referring to rq::cpu_load, " tip-bot2 for Colin Ian King
2023-10-10 21:47 ` tip-bot2 for Colin Ian King [this message]

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=169697447356.3135.18063293604947285416.tip-bot2@tip-bot2 \
    --to=tip-bot2@linutronix.de \
    --cc=colin.i.king@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.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®