From: Ingo Molnar <mingo@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: Peter Zijlstra <peterz@infradead.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Valentin Schneider <vschneid@redhat.com>
Subject: [PATCH 0/7] sched/balancing: Misc updates & cleanups
Date: Fri, 1 Mar 2024 12:09:44 +0100 [thread overview]
Message-ID: <20240301110951.3707367-1-mingo@kernel.org> (raw)
Improve a handful of things I noticed while looking through the
scheduler balancing code. No change in functionality intended.
Ingo Molnar (7):
sched/balancing: Switch the 'DEFINE_SPINLOCK(balancing)' spinlock into an 'atomic_t sched_balance_running' flag
sched/balancing: Change 'enum cpu_idle_type' to have more natural definitions
sched/balancing: Change comment formatting to not overlap Git conflict marker lines
sched/balancing: Fix comments (trying to) refer to NOHZ_BALANCE_KICK
sched/balancing: Update run_rebalance_domains() comments
sched/balancing: Vertically align the comments of 'struct sg_lb_stats' and 'struct sd_lb_stats'
sched/balancing: Update comments in 'struct sg_lb_stats' and 'struct sd_lb_stats'
include/linux/sched/idle.h | 3 +-
kernel/sched/fair.c | 104 +++++++++++++++++++++++++++++++++++++----------------------------
2 files changed, 60 insertions(+), 47 deletions(-)
--
2.40.1
next reply other threads:[~2024-03-01 11:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 11:09 Ingo Molnar [this message]
2024-03-01 11:09 ` [PATCH 1/7] sched/balancing: Switch the 'DEFINE_SPINLOCK(balancing)' spinlock into an 'atomic_t sched_balance_running' flag Ingo Molnar
2024-03-01 15:35 ` Shrikanth Hegde
2024-03-04 9:24 ` Ingo Molnar
2024-03-01 11:09 ` [PATCH 2/7] sched/balancing: Change 'enum cpu_idle_type' to have more natural definitions Ingo Molnar
2024-03-02 9:04 ` Shrikanth Hegde
2024-03-04 9:26 ` Ingo Molnar
2024-03-01 11:09 ` [PATCH 3/7] sched/balancing: Change comment formatting to not overlap Git conflict marker lines Ingo Molnar
2024-03-01 11:09 ` [PATCH 4/7] sched/balancing: Fix comments (trying to) refer to NOHZ_BALANCE_KICK Ingo Molnar
2024-03-01 11:23 ` [PATCH 4/7 v2] " Ingo Molnar
2024-03-01 11:09 ` [PATCH 5/7] sched/balancing: Update run_rebalance_domains() comments Ingo Molnar
2024-03-01 11:26 ` [PATCH 5/7 v2] " Ingo Molnar
2024-03-01 11:09 ` [PATCH 6/7] sched/balancing: Vertically align the comments of 'struct sg_lb_stats' and 'struct sd_lb_stats' Ingo Molnar
2024-03-01 11:09 ` [PATCH 7/7] sched/balancing: Update comments in " Ingo Molnar
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=20240301110951.3707367-1-mingo@kernel.org \
--to=mingo@kernel.org \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.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