From: Steven Rostedt <rostedt@goodmis.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: "Peter Zijlstra" <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
"Thomas Gleixner" <tglx@linutronix.de>,
"Paul E . McKenney" <paulmck@kernel.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"H . Peter Anvin" <hpa@zytor.com>, "Paul Turner" <pjt@google.com>,
linux-api@vger.kernel.org,
"Christian Brauner" <brauner@kernel.org>,
"Florian Weimer" <fw@deneb.enyo.de>,
David.Laight@ACULAB.COM, carlos@redhat.com,
"Peter Oskolkov" <posk@posk.io>,
"Alexander Mikhalitsyn" <alexander@mihalicyn.com>,
"Chris Kennelly" <ckennelly@google.com>,
"Ingo Molnar" <mingo@redhat.com>,
"Darren Hart" <dvhart@infradead.org>,
"Davidlohr Bueso" <dave@stgolabs.net>,
"André Almeida" <andrealmeid@igalia.com>,
libc-alpha@sourceware.org, "Jonathan Corbet" <corbet@lwn.net>
Subject: Re: [RFC PATCH 0/4] Extend rseq with sched_state field
Date: Wed, 17 May 2023 14:36:50 -0400 [thread overview]
Message-ID: <20230517143650.55eb8ce7@gandalf.local.home> (raw)
In-Reply-To: <20230517152654.7193-1-mathieu.desnoyers@efficios.com>
On Wed, 17 May 2023 11:26:50 -0400
Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote:
> This prototype extends struct rseq with a new sched_state field, which
> contains a "on-cpu" flag kept up-to-date by the scheduler.
>
> It is meant to be used by userspace adaptative mutexes to decide between
> busy-wait and futex wait system call (releasing the CPU) behaviors based
> on the current state of the mutex owner.
Woot!
I'm so glad I talked Jon into hanging around for André's spurious talk.
He's the one that brought up rseq (as he mentioned in his article), and I
guess you read that :-)
Unfortunately, I'm in the process of a lot of trips and
meetings/presentations over the next few weeks, and I will not be able to
look into this. But I hope that André could test it out.
Cheers!
-- Steve
prev parent reply other threads:[~2023-05-17 18:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 15:26 [RFC PATCH 0/4] Extend rseq with sched_state field Mathieu Desnoyers
2023-05-17 15:26 ` [RFC PATCH 1/4] rseq: Add sched_state field to struct rseq Mathieu Desnoyers
2023-05-17 16:03 ` Davidlohr Bueso
2023-05-18 21:49 ` Boqun Feng
2023-05-19 14:15 ` Mathieu Desnoyers
2023-05-19 17:18 ` Boqun Feng
2023-05-23 14:10 ` Mathieu Desnoyers
2023-05-19 20:51 ` Noah Goldstein
2023-05-23 12:49 ` Mathieu Desnoyers
2023-05-23 16:32 ` Noah Goldstein
2023-05-23 17:30 ` Mathieu Desnoyers
2023-05-23 20:10 ` Noah Goldstein
2023-05-17 15:26 ` [RFC PATCH 2/4] selftests/rseq: Add sched_state rseq field and getter Mathieu Desnoyers
2023-05-28 14:04 ` kernel test robot
2023-05-17 15:26 ` [RFC PATCH 3/4] selftests/rseq: Implement sched state test program Mathieu Desnoyers
2023-05-17 15:26 ` [RFC PATCH 4/4] selftests/rseq: Implement rseq_mutex " Mathieu Desnoyers
2023-05-17 16:07 ` [RFC PATCH 0/4] Extend rseq with sched_state field Davidlohr Bueso
2023-05-17 18:36 ` Steven Rostedt [this message]
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=20230517143650.55eb8ce7@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=David.Laight@ACULAB.COM \
--cc=alexander@mihalicyn.com \
--cc=andrealmeid@igalia.com \
--cc=boqun.feng@gmail.com \
--cc=brauner@kernel.org \
--cc=carlos@redhat.com \
--cc=ckennelly@google.com \
--cc=corbet@lwn.net \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=fw@deneb.enyo.de \
--cc=hpa@zytor.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=posk@posk.io \
--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;
as well as URLs for NNTP newsgroup(s).