From: Peter Zijlstra <peterz@infradead.org>
To: Prakash Sangappa <prakash.sangappa@oracle.com>
Cc: linux-kernel@vger.kernel.org, rostedt@goodmis.org,
tglx@linutronix.de, daniel.m.jordan@oracle.com,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [RFC PATCH 0/4] Scheduler time slice extension
Date: Wed, 13 Nov 2024 19:50:13 +0100 [thread overview]
Message-ID: <20241113185013.GA22571@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20241113000126.967713-1-prakash.sangappa@oracle.com>
On Wed, Nov 13, 2024 at 12:01:22AM +0000, Prakash Sangappa wrote:
> This patch set implements the above mentioned 50us extension time as posted
> by Peter. But instead of using restartable sequences as API to set the flag
> to request the extension, this patch proposes a new API with use of a per
> thread shared structure implementation described below. This shared structure
> is accessible in both users pace and kernel. The user thread will set the
> flag in this shared structure to request execution time extension.
But why -- we already have rseq, glibc uses it by default. Why add yet
another thing?
next prev parent reply other threads:[~2024-11-13 18:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 0:01 Prakash Sangappa
2024-11-13 0:01 ` [RFC PATCH 1/4] Introduce per thread user-kernel shared structure Prakash Sangappa
2024-11-13 0:01 ` [RFC PATCH 2/4] Scheduler time extention Prakash Sangappa
2024-11-13 3:57 ` K Prateek Nayak
2024-11-13 17:40 ` Prakash Sangappa
2024-11-13 0:01 ` [RFC PATCH 3/4] Indicate if schedular preemption delay request is granted Prakash Sangappa
2024-11-13 0:01 ` [RFC PATCH 4/4] Add scheduler preemption delay granted stats Prakash Sangappa
2024-11-13 5:43 ` [RFC PATCH 0/4] Scheduler time slice extension K Prateek Nayak
2024-11-13 19:56 ` Prakash Sangappa
2024-11-13 18:50 ` Peter Zijlstra [this message]
2024-11-13 19:36 ` Mathieu Desnoyers
2024-11-13 20:10 ` Prakash Sangappa
2024-11-13 20:57 ` Mathieu Desnoyers
2024-11-13 23:24 ` Prakash Sangappa
2024-11-14 10:28 ` Peter Zijlstra
2024-11-14 19:42 ` Prakash Sangappa
2024-11-15 14:13 ` Mathieu Desnoyers
2024-11-15 17:20 ` Prakash Sangappa
2024-12-09 20:36 ` Prakash Sangappa
2024-12-09 21:17 ` Mathieu Desnoyers
2024-12-16 18:59 ` Prakash Sangappa
2025-02-04 3:04 ` Prakash Sangappa
2024-11-14 10:14 ` Peter Zijlstra
2024-11-15 14:41 ` Mathieu Desnoyers
2024-11-15 17:49 ` Prakash Sangappa
2024-11-13 19:50 ` 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=20241113185013.GA22571@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=daniel.m.jordan@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=prakash.sangappa@oracle.com \
--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®