From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, sched-ext@meta.com,
David Vernet <void@manifault.com>
Subject: [GIT PULL] sched_ext: Fixes for v6.12-rc3
Date: Tue, 15 Oct 2024 10:38:35 -1000 [thread overview]
Message-ID: <Zw7Syx6dUES0a_R5@slm.duckdns.org> (raw)
The following changes since commit e0ed52154e866a1e9e9b97ded50b164698f0a222:
sched_ext: Documentation: Update instructions for running example schedulers (2024-10-08 08:49:18 -1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext.git/ tags/sched_ext-for-6.12-rc3-fixes
for you to fetch changes up to 60e339be100d7d49e13616bd8b4b1b864f0a64a0:
sched_ext: Remove unnecessary cpu_relax() (2024-10-14 13:23:49 -1000)
----------------------------------------------------------------
sched_ext: Fixes for v6.12-rc3
- More issues reported in the enable/disable paths on large machines with
many tasks due to scx_tasks_lock being held too long. Break up the task
iterations.
- Remove ops.select_cpu() dependency in bypass mode so that a misbehaving
implementation can't live-lock the machine by pushing all tasks to few
CPUs in bypass mode.
- Other misc fixes.
----------------------------------------------------------------
Björn Töpel (1):
selftests: sched_ext: Add sched_ext as proper selftest target
David Vernet (1):
sched_ext: Remove unnecessary cpu_relax()
Honglei Wang (1):
sched_ext: use correct function name in pick_task_scx() warning message
Tejun Heo (6):
Revert "sched_ext: Use shorter slice while bypassing"
sched_ext: Start schedulers with consistent p->scx.slice values
sched_ext: Move scx_buildin_idle_enabled check to scx_bpf_select_cpu_dfl()
sched_ext: bypass mode shouldn't depend on ops.select_cpu()
sched_ext: Move scx_tasks_lock handling into scx_task_iter helpers
sched_ext: Don't hold scx_tasks_lock for too long
kernel/sched/ext.c | 186 ++++++++++++++++-------------
tools/testing/selftests/Makefile | 9 +-
tools/testing/selftests/sched_ext/Makefile | 71 +++++------
3 files changed, 138 insertions(+), 128 deletions(-)
--
tejun
next reply other threads:[~2024-10-15 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 20:38 Tejun Heo [this message]
2024-10-16 20:51 ` [GIT PULL] sched_ext: Fixes for v6.12-rc3 pr-tracker-bot
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=Zw7Syx6dUES0a_R5@slm.duckdns.org \
--to=tj@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sched-ext@meta.com \
--cc=torvalds@linux-foundation.org \
--cc=void@manifault.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