From: Prakash Sangappa <prakash.sangappa@oracle.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"mathieu.desnoyers@efficios.com" <mathieu.desnoyers@efficios.com>,
"tglx@linutronix.de" <tglx@linutronix.de>
Subject: Re: [PATCH 0/2] Scheduler time extension
Date: Tue, 18 Mar 2025 16:10:09 +0000 [thread overview]
Message-ID: <821926D8-ABED-4B66-9E2D-39594DB82FA1@oracle.com> (raw)
In-Reply-To: <20250217120000.5ae1201a@gandalf.local.home>
> On Feb 17, 2025, at 9:00 AM, Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Sat, 15 Feb 2025 00:54:12 +0000
> Prakash Sangappa <prakash.sangappa@oracle.com> wrote:
>
>> Follow up to discussion in [1], posting these patches.
>> They are based on use of the restartable sequences(rseq) for API.
>>
>> However, currently the discussion is on thread [2] in response to patch
>> posted by Steven. Mainly about whether this feature should be applicable
>> only to normal threads(SCHED_OTHER) under PREEMPT_LAZY preemption model
>> or keep it independent of the preemption method.
>>
>> [1] https://lore.kernel.org/all/20241113000126.967713-1-prakash.sangappa@oracle.com/
>> [2] https://lore.kernel.org/all/20250131225837.972218232@goodmis.org/
>
> I'm still 100% against this delaying any non SCHED_OTHER task.
How do we proceed on this feature?
Are we leaning towards enabling this feature for SCHED_OTHER only under PREEMPT_LAZY?
-Prakash
>
> -- Steve
next prev parent reply other threads:[~2025-03-18 16:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-15 0:54 Prakash Sangappa
2025-02-15 0:54 ` [PATCH 1/2] Sched: Scheduler time slice extension Prakash Sangappa
2025-02-15 19:34 ` kernel test robot
2025-02-15 20:16 ` kernel test robot
2025-02-15 0:54 ` [PATCH 2/2] Sched: Add scheduler stat for cpu " Prakash Sangappa
2025-02-17 17:00 ` [PATCH 0/2] Scheduler time extension Steven Rostedt
2025-03-18 16:10 ` Prakash Sangappa [this message]
2025-03-22 10:14 ` Steven Rostedt
2025-04-11 20:54 ` Prakash Sangappa
2025-04-14 16:41 ` Steven Rostedt
2025-04-14 17:21 ` Prakash Sangappa
2025-04-15 6:25 ` Sebastian Andrzej Siewior
2025-04-18 19:38 ` Prakash Sangappa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=821926D8-ABED-4B66-9E2D-39594DB82FA1@oracle.com \
--to=prakash.sangappa@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®