[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <04E4EFD3-0FF1-475E-802B-97C72CBCC452@oracle.com>
Date: Wed, 4 Jun 2025 17:09:50 +0000
From: Prakash Sangappa <prakash.sangappa@...cle.com>
To: Steven Rostedt <rostedt@...dmis.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"peterz@...radead.org" <peterz@...radead.org>,
"mathieu.desnoyers@...icios.com" <mathieu.desnoyers@...icios.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"bigeasy@...utronix.de"
<bigeasy@...utronix.de>,
"kprateek.nayak@....com" <kprateek.nayak@....com>,
"vineethr@...ux.ibm.com" <vineethr@...ux.ibm.com>
Subject: Re: [PATCH V5 1/6] Sched: Scheduler time slice extension
> On Jun 4, 2025, at 7:31 AM, Steven Rostedt <rostedt@...dmis.org> wrote:
>
> On Tue, 3 Jun 2025 23:36:49 +0000
> Prakash Sangappa <prakash.sangappa@...cle.com> wrote:
>
>> @@ -2249,6 +2251,20 @@ static inline bool owner_on_cpu(struct task_struct *owner)
>> unsigned long sched_cpu_util(int cpu);
>> #endif /* CONFIG_SMP */
>>
>> +#ifdef CONFIG_RSEQ
>> +
>> +extern bool rseq_delay_resched(void);
>> +extern void rseq_delay_resched_fini(void);
>> +extern void rseq_delay_resched_tick(void);
>> +
>> +#else
>> +
>> +static inline bool rseq_delay_resched(void) { return false; }
>> +static inline void rseq_delay_resched_fini(void) { }
>> +static inline void rseq_delay_resched_tick(void) { }
>> +
>> +#endif
>> +
>
> Can we add a config to make this optional. I don't want to allow any task
> to have an extended timeslice over RT tasks regardless of how small the
> delay is.
Are you suggesting including a CONFIG to enable this feature or
to choose to be applicable to PREEMPT_LAZY task only?
>
> -- Steve
Powered by blists - more mailing lists