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