messages from 2026-11-20 20:42:34 to 2026-11-20 20:42:51 UTC [more...]
[PATCH v10 00/40] sched/deadline: bandwidth accounting fixes and selftests
2026-11-20 20:42 UTC (39+ messages)
` [PATCH v10 03/40] sched/deadline: Record the root domain holding a task's bandwidth
` [PATCH v10 04/40] sched/deadline: Leave a dying task out of a rebuild of the accounting
` [PATCH v10 05/40] selftests/sched: Test SCHED_DEADLINE bandwidth across a root domain rebuild
` [PATCH v10 06/40] selftests/sched: Test the root domain rebuild in deadline_bw_test
` [PATCH v10 07/40] sched/deadline: Move a task's bandwidth only where room was made
` [PATCH v10 08/40] cgroup/cpuset: Wait for an attach before rebuilding the sched domains
` [PATCH v10 09/40] sched: Make deadline policy and affinity changes wait for a cpuset attach
` [PATCH v10 10/40] cgroup/cpuset: Give back the bandwidth an attach did not move
` [PATCH v10 11/40] cgroup/cpuset: Reserve the bandwidth in the root domain a task moves to
` [PATCH v10 12/40] selftests/sched: Test cpuset moves in deadline_bw_test
` [PATCH v10 13/40] sched/deadline: Make a rebuild count a task in the root domain it runs in
` [PATCH v10 14/40] sched/deadline: Move a task's bandwidth to "
` [PATCH v10 15/40] sched/deadline: Keep a task in the root domain that counts its bandwidth
` [PATCH v10 16/40] sched/deadline: Keep the last CPU a task has in its root domain
` [PATCH v10 17/40] cgroup/cpuset: Refuse to take a deadline task out of "
` [PATCH v10 18/40] selftests/sched: Test the root domain of a task in deadline_bw_test
` [PATCH v10 19/40] sched/deadline: Count only active CPUs when spreading extra_bw
` [PATCH v10 20/40] sched/deadline: Do not truncate a bandwidth to 32 bits in __dl_add/sub()
` [PATCH v10 21/40] rtmutex: Continue the chain walk when a waiter's deadline donor changes
` [PATCH v10 22/40] rtmutex: Do not stop the chain walk at an owner whose top waiter changed
` [PATCH v10 23/40] sched/deadline: Hold a reference on the deadline donor of a boosted task
` [PATCH v10 24/40] selftests/sched: Test the rtmutex chain walk in deadline_bw_test
` [PATCH v10 25/40] sched/deadline: Reset the donor's runtime at a deboost in the class
` [PATCH v10 26/40] sched/deadline: Replenish a throttled task boosted while asleep
` [PATCH v10 27/40] sched/deadline: Count the bandwidth a boosted task is given
` [PATCH v10 28/40] sched/deadline: Start a period for a task that enters the class blocked
` [PATCH v10 29/40] sched/deadline: Start a period at a deboost out of the class
` [PATCH v10 30/40] sched/deadline: Start a period for a task requeued onto an rt_mutex
` [PATCH v10 31/40] selftests/sched: Test deadline boosts in deadline_bw_test
` [PATCH v10 32/40] sched/deadline: Cancel the replenishment timer with the parameters
` [PATCH v10 33/40] sched/deadline: Cap the runtime left of a constrained task at dl_runtime
` [PATCH v10 34/40] sched/deadline: Check the runtime of a task that comes back runnable
` [PATCH v10 35/40] sched/deadline: Check the runtime of a task whose parameters change
` [PATCH v10 36/40] sched/deadline: Reschedule a running task throttled at its enqueue
` [PATCH v10 37/40] sched/deadline: Keep the start of the period across a change of dl_deadline
` [PATCH v10 38/40] sched/deadline: Boost an owner that cannot run on its own reservation
` [PATCH v10 39/40] selftests/sched: Test parameter changes in deadline_bw_test
` [PATCH v10 40/40] selftests/sched: Share the helpers of the deadline tests
page: | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox