From: trix@redhat.com
To: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
bristot@redhat.com
Cc: linux-kernel@vger.kernel.org, Tom Rix <trix@redhat.com>
Subject: [PATCH] sched/fair: cleanup master/slave usage in wake_wide()
Date: Sun, 30 May 2021 12:30:39 -0700 [thread overview]
Message-ID: <20210530193039.2556526-1-trix@redhat.com> (raw)
From: Tom Rix <trix@redhat.com>
From Documentation/process/coding-style section for
inclusive terminology, make these variable name changes in
wake_wide()
master -> primary
slave -> secondary
Signed-off-by: Tom Rix <trix@redhat.com>
---
kernel/sched/fair.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 161b92aa1c79..ade9f065c690 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -5754,13 +5754,13 @@ static void record_wakee(struct task_struct *p)
*/
static int wake_wide(struct task_struct *p)
{
- unsigned int master = current->wakee_flips;
- unsigned int slave = p->wakee_flips;
+ unsigned int primary = current->wakee_flips;
+ unsigned int secondary = p->wakee_flips;
int factor = __this_cpu_read(sd_llc_size);
- if (master < slave)
- swap(master, slave);
- if (slave < factor || master < slave * factor)
+ if (primary < secondary)
+ swap(primary, secondary);
+ if (secondary < factor || primary < secondary * factor)
return 0;
return 1;
}
--
2.26.3
next reply other threads:[~2021-05-30 19:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-30 19:30 trix [this message]
2021-05-31 7:18 ` Peter Zijlstra
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=20210530193039.2556526-1-trix@redhat.com \
--to=trix@redhat.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.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®