From: Steven Rostedt <rostedt@goodmis.org>
To: Prakash Sangappa <prakash.sangappa@oracle.com>
Cc: Madadi Vineeth Reddy <vineethr@linux.ibm.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"mathieu.desnoyers@efficios.com" <mathieu.desnoyers@efficios.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"bigeasy@linutronix.de" <bigeasy@linutronix.de>,
"kprateek.nayak@amd.com" <kprateek.nayak@amd.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V4 1/6] Sched: Scheduler time slice extension
Date: Tue, 20 May 2025 16:20:35 -0400 [thread overview]
Message-ID: <20250520162035.7855e94c@gandalf.local.home> (raw)
In-Reply-To: <3EF0AA39-2C51-4E70-975C-CF8BBF27DAE4@oracle.com>
On Tue, 20 May 2025 16:52:20 +0000
Prakash Sangappa <prakash.sangappa@oracle.com> wrote:
> But the thread has to make the sched_yied() call. The behavior of which
> will be different if called in the extended time vs not. Assume this is ok.
I assume it is ;-)
That's because the only time user space should ever call sched_yield() in
an extended time slice is because it wants to tell the kernel it doesn't
need it anymore. If that's not the case, that means one it's using the
extended time slice and calling sched_yield() for some other reason, which
doesn't make any sense.
-- Steve
next prev parent reply other threads:[~2025-05-20 20:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 21:45 [PATCH V4 0/6] " Prakash Sangappa
2025-05-13 21:45 ` [PATCH V4 1/6] Sched: " Prakash Sangappa
2025-05-14 10:58 ` Madadi Vineeth Reddy
2025-05-14 23:12 ` Prakash Sangappa
2025-05-15 9:01 ` Steven Rostedt
2025-05-20 16:52 ` Prakash Sangappa
2025-05-20 20:20 ` Steven Rostedt [this message]
2025-05-23 20:06 ` Mathieu Desnoyers
2025-05-23 20:34 ` Prakash Sangappa
2025-05-13 21:45 ` [PATCH V4 2/6] Sched: Indicate if thread got rescheduled Prakash Sangappa
2025-05-13 21:45 ` [PATCH V4 3/6] Sched: Tunable to specify duration of time slice extension Prakash Sangappa
2025-05-14 11:21 ` kernel test robot
2025-05-13 21:45 ` [PATCH V4 4/6] Sched: Add scheduler stat for cpu " Prakash Sangappa
2025-05-14 12:37 ` Madadi Vineeth Reddy
2025-05-14 23:01 ` Prakash Sangappa
2025-05-13 21:45 ` [PATCH V4 5/6] Sched: Add tracepoint for sched " Prakash Sangappa
2025-05-13 21:45 ` [PATCH V4 6/6] Add API to query supported rseq cs flags Prakash Sangappa
2025-05-23 19:57 ` Mathieu Desnoyers
2025-05-23 20:03 ` Prakash Sangappa
2025-05-20 21:01 ` [PATCH V4 0/6] Scheduler time slice extension 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=20250520162035.7855e94c@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bigeasy@linutronix.de \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=peterz@infradead.org \
--cc=prakash.sangappa@oracle.com \
--cc=tglx@linutronix.de \
--cc=vineethr@linux.ibm.com \
/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®