From: David Vernet <void@manifault.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
bsegall@google.com, bristot@redhat.com, vschneid@redhat.com,
kernel-team@meta.com
Subject: [PATCH v3 0/3] sched/fair: Simplify and optimize update_sd_pick_busiest()
Date: Mon, 5 Feb 2024 22:39:18 -0600 [thread overview]
Message-ID: <20240206043921.850302-1-void@manifault.com> (raw)
update_sd_pick_busiest() (and its caller) has some room for small
optimizations, and some improvements in readability.
- In update_sd_lb_stats(), we're using a goto to skip a single if check.
Let's remove the goto and just add another condition to the if.
- In update_sd_pick_busiest(), only update a group_misfit_task group to
be the busiest if it has strictly more load than the current busiest
task, rather than >= the load.
- When comparing the current struct sched_group with the yet-busiest
domain in update_sd_pick_busiest(), if the two groups have the same
group type, we're currently doing a bit of unnecessary work for any
group >= group_misfit_task. We're comparing the two groups, and then
returning only if false (the group in question is not the busiest).
Othewise, we break, do an extra unnecessary conditional check that's
vacuously false for any group type > group_fully_busy, and then always
return true. This patch series has us instead simply return directly
in the switch statement, saving some bytes in load_balance().
---
v1: https://lore.kernel.org/lkml/20240202070216.2238392-1-void@manifault.com/
v2: https://lore.kernel.org/all/20240204044618.46100-1-void@manifault.com/
v2 -> v3:
- Add Vincent's Reviewed-by tags
- Fix stale commit summary sentence (Vincent)
v1 -> v2 changes:
- Split the patch series into separate patches (Valentin)
- Update the group_misfit_task busiest check to use strict inequality
David Vernet (3):
sched/fair: Remove unnecessary goto in update_sd_lb_stats()
sched/fair: Do strict inequality check for busiest misfit task group
sched/fair: Simplify some logic in update_sd_pick_busiest()
kernel/sched/fair.c | 19 ++++---------------
1 file changed, 4 insertions(+), 15 deletions(-)
--
2.43.0
next reply other threads:[~2024-02-06 4:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 4:39 David Vernet [this message]
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: sched/core] " tip-bot2 for David Vernet
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=20240206043921.850302-1-void@manifault.com \
--to=void@manifault.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
/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