[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <A276BE8D-B05F-4635-BB5B-3481C7DA5C31@oracle.com>
Date: Fri, 18 Apr 2025 19:38:02 +0000
From: Prakash Sangappa <prakash.sangappa@...cle.com>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
CC: Steven Rostedt <rostedt@...dmis.org>,
"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>
Subject: Re: [PATCH 0/2] Scheduler time extension
> On Apr 14, 2025, at 11:25 PM, Sebastian Andrzej Siewior <bigeasy@...utronix.de> wrote:
>
> On 2025-04-14 12:41:49 [-0400], Steven Rostedt wrote:
>> On Fri, 11 Apr 2025 20:54:14 +0000
>> Prakash Sangappa <prakash.sangappa@...cle.com> wrote:
>>
>>>> On Mar 22, 2025, at 3:14 AM, Steven Rostedt <rostedt@...dmis.org> wrote:
>>>>
>>>> On Tue, 18 Mar 2025 16:10:09 +0000
>>>> Prakash Sangappa <prakash.sangappa@...cle.com> wrote:
>>>>
>>>>> How do we proceed on this feature?
>>>>> Are we leaning towards enabling this feature for SCHED_OTHER only under PREEMPT_LAZY?
>>>>
>>>> The merge window is about to open and I'm way behind in what needs to go in.
>>>>
>>>> Let's continue this discussion after rc1 comes out.
>>>
>>> Can the API be finalized? We have an use case which will benefit from it. So like to see this feature
>>> merged.
>>
>> I'm still not for SCHED_OTHER tasks being allowed to delay RT or deadline
>> tasks, even for 5us. But if that's what Peter wants, I'm not going to nack
>> it.
>
> I tried to explain in
> https://lore.kernel.org/all/20250206150152.-5Fauhtm@linutronix.de
>
> that I don't see how this delay could work for PREEMPT_RT.
>
>> Just keep it configurable so that it can be easily disabled, as I have no
>> intentions of using it.
>
> same here.
Posted a V2 patch.
https://lore.kernel.org/all/20250418193410.2010058-1-prakash.sangappa@oracle.com/
Prakash
>
>> -- Steve
>
> Sebastian
Powered by blists - more mailing lists