Linux cgroups development
 help / color / mirror / Atom feed
 messages from 2026-11-19 19:07:17 to 2026-11-19 19:19:34 UTC [more...]

[PATCH] kernfs: allocate in open before taking the active reference
 2026-11-19 19:19 UTC 

[PATCH v5 00/17] sched/deadline: first bandwidth accounting fixes and selftests
 2026-11-19 19:07 UTC  (18+ messages)
` [PATCH v5 01/17] sched: Refuse SCHED_FLAG_KEEP_PARAMS that would change the policy or the class
` [PATCH v5 02/17] sched/deadline: Do not admit bandwidth for parameters that are kept
` [PATCH v5 03/17] sched: Let a task boosted by a deadline waiter change its policy
` [PATCH v5 04/17] sched/deadline: Do not divide by zero active CPUs of a root domain
` [PATCH v5 05/17] sched/deadline: Refuse dl_server debugfs writes while the rq is offline
` [PATCH v5 06/17] sched: Take cpuset_mutex for a deadline policy change only with pi
` [PATCH v5 07/17] sched/deadline: Do not lose a throttled task switched out and back
` [PATCH v5 08/17] sched/deadline: Do not replenish a boost from cleared parameters
` [PATCH v5 09/17] sched/deadline: Reset the deadline and the runtime with the parameters
` [PATCH v5 10/17] sched/deadline: Fix an overflow of the 0-lag time with long periods
` [PATCH v5 11/17] sched/deadline: Release the bandwidth of a task that leaves the class asleep
` [PATCH v5 12/17] sched/deadline: Reject SCHED_DEADLINE on exited tasks
` [PATCH v5 13/17] sched/deadline: Fix this_bw when a task is changed during a remote wakeup
` [PATCH v5 14/17] sched/deadline: Check SCHED_DEADLINE affinity under the rq lock
` [PATCH v5 15/17] sched/debug: Show the deadline bandwidth of each runqueue
` [PATCH v5 16/17] selftests/sched: Add a test of SCHED_DEADLINE policy round trips
` [PATCH v5 17/17] 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