From: Valentin Schneider <valentin.schneider@arm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@redhat.com, peterz@infradead.org,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com
Subject: [RFC PATCH 3/7] sched/fair: find_idlest_group(): Remove unused sd_flag parameter
Date: Wed, 11 Dec 2019 16:43:57 +0000 [thread overview]
Message-ID: <20191211164401.5013-4-valentin.schneider@arm.com> (raw)
In-Reply-To: <20191211164401.5013-1-valentin.schneider@arm.com>
The last use of that parameter was removed by commit
57abff067a08 ("sched/fair: Rework find_idlest_group()")
Get rid of the parameter.
Signed-off-by: Valentin Schneider <valentin.schneider@arm.com>
---
kernel/sched/fair.c | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index a614e4794024..f0b2b403bebb 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -5575,8 +5575,7 @@ static int wake_affine(struct sched_domain *sd, struct task_struct *p,
}
static struct sched_group *
-find_idlest_group(struct sched_domain *sd, struct task_struct *p,
- int this_cpu, int sd_flag);
+find_idlest_group(struct sched_domain *sd, struct task_struct *p, int this_cpu);
/*
* find_idlest_group_cpu - find the idlest CPU among the CPUs in the group.
@@ -5665,7 +5664,7 @@ static inline int find_idlest_cpu(struct sched_domain *sd, struct task_struct *p
continue;
}
- group = find_idlest_group(sd, p, cpu, sd_flag);
+ group = find_idlest_group(sd, p, cpu);
if (!group) {
sd = sd->child;
continue;
@@ -8382,8 +8381,7 @@ static bool update_pick_idlest(struct sched_group *idlest,
* Assumes p is allowed on at least one CPU in sd.
*/
static struct sched_group *
-find_idlest_group(struct sched_domain *sd, struct task_struct *p,
- int this_cpu, int sd_flag)
+find_idlest_group(struct sched_domain *sd, struct task_struct *p, int this_cpu)
{
struct sched_group *idlest = NULL, *local = NULL, *group = sd->groups;
struct sg_lb_stats local_sgs, tmp_sgs;
--
2.24.0
next prev parent reply other threads:[~2019-12-11 16:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 16:43 [RFC PATCH 0/7] sched: Streamline select_task_rq() & select_task_rq_fair() Valentin Schneider
2019-12-11 16:43 ` [RFC PATCH 1/7] sched: Add WF_TTWU, WF_EXEC wakeup flags Valentin Schneider
2019-12-11 16:43 ` [RFC PATCH 2/7] sched: Kill select_task_rq()'s sd_flag parameter Valentin Schneider
2019-12-11 16:43 ` Valentin Schneider [this message]
2019-12-11 16:43 ` [RFC PATCH 4/7] sched/fair: Dissociate wakeup decisions from SD flag value Valentin Schneider
2019-12-11 16:53 ` Valentin Schneider
2019-12-11 16:43 ` [RFC PATCH 5/7] sched/topology: Make {lowest/highest}_flag_domain() work with > 1 flags Valentin Schneider
2019-12-11 16:44 ` [RFC PATCH 6/7] sched/fair: Split select_task_rq_fair want_affine logic Valentin Schneider
2019-12-11 16:44 ` [RFC PATCH 7/7] sched/topology: Define and use shortcut pointers for wakeup sd_flag scan Valentin Schneider
2020-01-06 8:10 ` [RFC PATCH 0/7] sched: Streamline select_task_rq() & select_task_rq_fair() 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=20191211164401.5013-4-valentin.schneider@arm.com \
--to=valentin.schneider@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).