Linux cgroups development
 help / color / mirror / Atom feed
 messages from 2026-11-16 19:06:08 to 2026-11-16 20:04:49 UTC [more...]

[PATCH] mm: workingset: compare shadow nodes node-wide without kmem accounting
 2026-11-16 20:04 UTC  (3+ messages)

[PATCH] blk-ioprio: check capabilities before promoting a cgroup to RT
 2026-11-16 19:07 UTC  (2+ messages)

[PATCH v6 00/37] sched/deadline: bandwidth accounting fixes and selftests
 2026-11-16 19:05 UTC  (18+ messages)
` [PATCH v6 19/37] sched/deadline: Move a task's bandwidth only where room was made
` [PATCH v6 22/37] cgroup/cpuset: Give back the bandwidth an attach did not move
` [PATCH v6 23/37] cgroup/cpuset: Reserve the bandwidth in the root domain a task moves to
` [PATCH v6 24/37] sched/deadline: Make a rebuild count a task in the root domain it runs in
` [PATCH v6 25/37] sched/deadline: Move a task's bandwidth to "
` [PATCH v6 26/37] sched/deadline: Keep a task in the root domain that counts its bandwidth
` [PATCH v6 27/37] sched/deadline: Keep the last CPU a task has in its root domain
` [PATCH v6 28/37] cgroup/cpuset: Refuse to take a deadline task out of "
` [PATCH v6 29/37] sched/deadline: Cancel the replenishment timer with the parameters
` [PATCH v6 30/37] sched/deadline: Count the bandwidth a boosted task is given
` [PATCH v6 31/37] sched/deadline: Start a period for a task that enters the class blocked
` [PATCH v6 32/37] sched/deadline: Check the runtime of a task that comes back runnable
` [PATCH v6 33/37] sched/deadline: Check the runtime of a task whose parameters change
` [PATCH v6 34/37] sched/debug: Show the deadline bandwidth of each runqueue
` [PATCH v6 35/37] selftests/sched: Add a test of SCHED_DEADLINE policy round trips
` [PATCH v6 36/37] selftests/sched: Test SCHED_DEADLINE bandwidth across a root domain rebuild
` [PATCH v6 37/37] selftests/sched: Add a test of SCHED_DEADLINE bandwidth accounting


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox