Thread (35 messages) flat view 35 messages, 6 authors, 2025-02-12

Re: [RFC][PATCH 1/2] sched: Extended scheduler time slice

From: Joel Fernandes <hidden>
Date: 2025-02-05 00:56:22
Also in: linux-mm, lkml

On Feb 4, 2025, at 5:44 PM, Prakash Sangappa [off-list ref] wrote:


quoted
On Feb 1, 2025, at 10:11 AM, Peter Zijlstra [off-list ref] wrote:
quoted
On Sat, Feb 01, 2025 at 07:47:32AM -0500, Steven Rostedt wrote:


On February 1, 2025 6:59:06 AM EST, Peter Zijlstra [off-list ref] wrote:
quoted
I still have full hate for this approach.
So what approach would you prefer?
The one that does not rely on the preemption method -- I think I posted
something along those line, and someone else recently reposted something
bsaed on it.
Here is the RFC I had sent that Peter is referring
FWIW, I second the idea of a new syscall for this than (ab)using rseq
and also independence from preemption method. I agree that something
generic is better than relying on preemption method.

thanks,

 - Joel



Tying things to the preemption method is absurdly bad design -- and I've
quoted
told you that before.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help