From: "tip-bot2 for David Vernet" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: David Vernet <void@manifault.com>, Ingo Molnar <mingo@kernel.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Valentin Schneider <vschneid@redhat.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: sched/core] sched/fair: Do strict inequality check for busiest misfit task group
Date: Wed, 28 Feb 2024 22:00:09 -0000 [thread overview]
Message-ID: <170915760926.398.7923117841020138205.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20240206043921.850302-3-void@manifault.com>
The following commit has been merged into the sched/core branch of tip:
Commit-ID: 7f1a7229718d788f26a711374da83adc2689837f
Gitweb: https://git.kernel.org/tip/7f1a7229718d788f26a711374da83adc2689837f
Author: David Vernet <void@manifault.com>
AuthorDate: Mon, 05 Feb 2024 22:39:20 -06:00
Committer: Ingo Molnar <mingo@kernel.org>
CommitterDate: Wed, 28 Feb 2024 15:19:24 +01:00
sched/fair: Do strict inequality check for busiest misfit task group
In update_sd_pick_busiest(), when comparing two sched groups that are
both of type group_misfit_task, we currently consider the new group as
busier than the current busiest group even if the new group has the
same misfit task load as the current busiest group. We can avoid some
unnecessary writes if we instead only consider the newest group to be
the busiest if it has a higher load than the current busiest. This
matches the behavior of other group types where we compare load, such as
two groups that are both overloaded.
Let's update the group_misfit_task type comparison to also only update
the busiest group in the event of strict inequality.
Signed-off-by: David Vernet <void@manifault.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Reviewed-by: Vincent Guittot <vincent.guittot@linaro.org>
Reviewed-by: Valentin Schneider <vschneid@redhat.com>
Link: https://lore.kernel.org/r/20240206043921.850302-3-void@manifault.com
---
kernel/sched/fair.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 41dda53..448520f 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -10032,7 +10032,7 @@ static bool update_sd_pick_busiest(struct lb_env *env,
* If we have more than one misfit sg go with the biggest
* misfit.
*/
- if (sgs->group_misfit_task_load < busiest->group_misfit_task_load)
+ if (sgs->group_misfit_task_load <= busiest->group_misfit_task_load)
return false;
break;
next prev parent reply other threads:[~2024-02-28 22:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 4:39 [PATCH v3 0/3] sched/fair: Simplify and optimize update_sd_pick_busiest() David Vernet
2024-02-06 4:39 ` [PATCH v3 1/3] sched/fair: Remove unnecessary goto in update_sd_lb_stats() David Vernet
2024-02-28 22:00 ` [tip: sched/core] " tip-bot2 for David Vernet
2024-02-06 4:39 ` [PATCH v3 2/3] sched/fair: Do strict inequality check for busiest misfit task group David Vernet
2024-02-06 13:17 ` Valentin Schneider
2024-02-28 22:00 ` tip-bot2 for David Vernet [this message]
2024-02-06 4:39 ` [PATCH v3 3/3] sched/fair: Simplify some logic in update_sd_pick_busiest() David Vernet
2024-02-28 22:00 ` [tip: sched/core] sched/fair: Simplify the update_sd_pick_busiest() logic tip-bot2 for David Vernet
2024-02-16 19:44 ` [PATCH v3 0/3] sched/fair: Simplify and optimize update_sd_pick_busiest() David Vernet
2024-02-26 17:50 ` David Vernet
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=170915760926.398.7923117841020138205.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=void@manifault.com \
--cc=vschneid@redhat.com \
--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®