From: Ingo Molnar <mingo@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: Peter Zijlstra <peterz@infradead.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Shrikanth Hegde <sshegde@linux.ibm.com>,
Valentin Schneider <vschneid@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>
Subject: [PATCH 0/5] sched: Split out kernel/sched/fair_balance.c, numa_balancing.c and syscalls.c, plus other updates
Date: Sun, 7 Apr 2024 10:43:14 +0200 [thread overview]
Message-ID: <20240407084319.1462211-1-mingo@kernel.org> (raw)
kernel/sched/core.c and fair.c have become a hodgepodge of scheduler
functionality that obscures core scheduling and fair-balancing
class scheduling functionality quite a bit.
Improve it all a bit by splitting syscall.c out of core.c, and
fair_balance.c and numa_balancing.c out of fair.c:
# of Lines of code
BEFORE => AFTER
---------------
kernel/sched/sched.h 3493 => 3891
kernel/sched/core.c 12067 => 10308
kernel/sched/syscalls.c - => 1691
kernel/sched/fair.c 13295 => 5707
kernel/sched/fair_balance.c - => 5103
kernel/sched/numa_balancing.c - => 2277
total 49650 => 49765
This is only a first-approximation split.
Thanks,
Ingo
=================>
Ingo Molnar (5):
sched: Split out kernel/sched/syscalls.c from kernel/sched/core.c
sched: Split out kernel/sched/fair_balance.c from kernel/sched/fair.c
sched: Split out kernel/sched/numa_balancing.c from kernel/sched/fair.c
sched/fair: Remove NEXT_BUDDY
sched/fair: Rename set_next_buddy() to set_next_pick()
kernel/sched/Makefile | 3 +
kernel/sched/core.c | 1951 +--------
kernel/sched/fair.c | 13184 +++++++++++++-----------------------------------------------
kernel/sched/fair_balance.c | 5103 +++++++++++++++++++++++
kernel/sched/features.h | 7 -
kernel/sched/numa_balancing.c | 2277 +++++++++++
kernel/sched/sched.h | 400 +-
kernel/sched/syscalls.c | 1691 ++++++++
8 files changed, 12367 insertions(+), 12249 deletions(-)
create mode 100644 kernel/sched/fair_balance.c
create mode 100644 kernel/sched/numa_balancing.c
create mode 100644 kernel/sched/syscalls.c
--
2.40.1
next reply other threads:[~2024-04-07 8:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-07 8:43 Ingo Molnar [this message]
2024-04-07 8:43 ` [PATCH 1/5] sched: Split out kernel/sched/syscalls.c from kernel/sched/core.c Ingo Molnar
2024-04-07 19:09 ` kernel test robot
2024-05-27 12:05 ` [tip: sched/core] sched/syscalls: " tip-bot2 for Ingo Molnar
2024-04-07 8:43 ` [PATCH 2/5] sched: Split out kernel/sched/fair_balance.c from kernel/sched/fair.c Ingo Molnar
2024-04-07 10:04 ` kernel test robot
2024-04-07 10:15 ` kernel test robot
2024-04-07 20:21 ` kernel test robot
2024-04-07 8:43 ` [PATCH 3/5] sched: Split out kernel/sched/numa_balancing.c " Ingo Molnar
2024-04-07 18:49 ` kernel test robot
2024-04-07 8:43 ` [PATCH 4/5] sched/fair: Remove NEXT_BUDDY Ingo Molnar
2024-04-07 8:43 ` [PATCH 5/5] sched/fair: Rename set_next_buddy() to set_next_pick() Ingo Molnar
2024-04-08 9:16 ` Peter Zijlstra
2024-04-09 8:32 ` Ingo Molnar
2024-04-09 9:27 ` 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=20240407084319.1462211-1-mingo@kernel.org \
--to=mingo@kernel.org \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sshegde@linux.ibm.com \
--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