From: Peter Oskolkov <posk@google.com>
To: Peter Zijlstra <peterz@infradead.org>,
mingo@redhat.com, tglx@linutronix.de, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
bristot@redhat.com
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-api@vger.kernel.org, x86@kernel.org, pjt@google.com,
posk@google.com, avagin@google.com, jannh@google.com,
tdelisle@uwaterloo.ca, posk@posk.io
Subject: [RFC PATCH v2 0/5] User Managed Concurrency Groups
Date: Thu, 13 Jan 2022 15:39:35 -0800 [thread overview]
Message-ID: <20220113233940.3608440-1-posk@google.com> (raw)
This adds two small patches on top of peterz@'s RFC from
https://lore.kernel.org/lkml/20211214204445.665580974@infradead.org/
The new patches are not fully tested - I'm still working on it.
I'll post another patch shortly that adds worker timeouts in
sys_umcg_wait().
Sending this out just to break the silence and to assess if the
approach I'm taking here is not strongly NACKed.
Peter Oskolkov (3):
sched/umcg: add WF_CURRENT_CPU and externise ttwu
sched: UMCG: add a blocked worker list
sched: UMCG: allow to sys_umcg_kick UMCG servers
Peter Zijlstra (2):
x86/uaccess: Implement unsafe_try_cmpxchg_user()
sched: User Mode Concurency Groups
arch/x86/Kconfig | 1 +
arch/x86/entry/syscalls/syscall_64.tbl | 3 +
arch/x86/include/asm/thread_info.h | 2 +
arch/x86/include/asm/uaccess.h | 57 ++
fs/exec.c | 1 +
include/linux/entry-common.h | 6 +
include/linux/sched.h | 86 +++
include/linux/syscalls.h | 4 +
include/linux/thread_info.h | 2 +
include/uapi/asm-generic/unistd.h | 9 +-
include/uapi/linux/umcg.h | 161 +++++
init/Kconfig | 15 +
kernel/entry/common.c | 18 +-
kernel/exit.c | 5 +
kernel/sched/Makefile | 1 +
kernel/sched/core.c | 12 +-
kernel/sched/fair.c | 4 +
kernel/sched/sched.h | 15 +-
kernel/sched/umcg.c | 913 +++++++++++++++++++++++++
kernel/sys_ni.c | 5 +
20 files changed, 1305 insertions(+), 15 deletions(-)
create mode 100644 include/uapi/linux/umcg.h
create mode 100644 kernel/sched/umcg.c
base-commit: 85538cc07d6b6dcffc1df64a22308fcb05ecddf4
--
2.34.1.703.g22d0c6ccf7-goog
next reply other threads:[~2022-01-13 23:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 23:39 Peter Oskolkov [this message]
2022-01-13 23:39 ` [RFC PATCH v2 1/5] sched/umcg: add WF_CURRENT_CPU and externise ttwu Peter Oskolkov
2022-01-13 23:39 ` [RFC PATCH v2 2/5] x86/uaccess: Implement unsafe_try_cmpxchg_user() Peter Oskolkov
2022-01-13 23:39 ` [RFC PATCH v2 3/5] sched: User Mode Concurency Groups Peter Oskolkov
2022-01-13 23:39 ` [RFC PATCH v2 4/5] sched: UMCG: add a blocked worker list Peter Oskolkov
2022-01-17 9:19 ` Peter Zijlstra
2022-01-18 17:16 ` Peter Oskolkov
2022-01-27 15:37 ` Peter Zijlstra
2022-01-27 17:20 ` Peter Oskolkov
2022-01-13 23:39 ` [RFC PATCH v2 5/5] sched: UMCG: allow to sys_umcg_kick UMCG servers Peter Oskolkov
2022-01-27 16:35 ` Peter Zijlstra
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=20220113233940.3608440-1-posk@google.com \
--to=posk@google.com \
--cc=avagin@google.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=jannh@google.com \
--cc=juri.lelli@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=posk@posk.io \
--cc=rostedt@goodmis.org \
--cc=tdelisle@uwaterloo.ca \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.