From: Peter Zijlstra <peterz@infradead.org>
To: Peter Oskolkov <posk@posk.io>
Cc: Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
juri.lelli@redhat.com,
Vincent Guittot <vincent.guittot@linaro.org>,
dietmar.eggemann@arm.com, Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>,
mgorman@suse.de, bristot@redhat.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
linux-api@vger.kernel.org, x86@kernel.org,
Paul Turner <pjt@google.com>, Peter Oskolkov <posk@google.com>,
Andrei Vagin <avagin@google.com>, Jann Horn <jannh@google.com>,
Thierry Delisle <tdelisle@uwaterloo.ca>
Subject: Re: [RFC][PATCH 0/3] sched: User Managed Concurrency Groups
Date: Wed, 15 Dec 2021 11:06:20 +0100 [thread overview]
Message-ID: <Ybm+HJzkO/0BB4Va@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAFTs51XRJj1pwF6q5hwdGP0jtXmY81QQmTzyuA26fHMH0zCymw@mail.gmail.com>
On Tue, Dec 14, 2021 at 07:46:25PM -0800, Peter Oskolkov wrote:
> On Tue, Dec 14, 2021 at 12:55 PM Peter Zijlstra <peterz@infradead.org> wrote:
> >
> > Hi,
> >
> > This is actually tested code; but still missing the SMP wake-to-idle machinery.
> > I still need to think about that.
>
> Thanks, Peter!
>
> At a first glance, your main patch does not look much smaller than
> mine, and I thought the whole point of re-doing it was to throw away
> extra features and make things smaller/simpler...
Well, simpler was the goal. I didn't really focus on size much. It isn't
really big to begin with.
But yes, it has 5 hooks now, 3 syscalls and lots of comments and all
that under 900 lines, not bad I'd say.
Also I think you wanted something like this? I'm not sure of the LAZY
name, but I can't seem to come up with anything saner atm.
---
--- a/include/linux/sched.h
+++ b/include/linux/sched.h
@@ -1297,6 +1297,7 @@ struct task_struct {
#ifdef CONFIG_UMCG
/* setup by sys_umcg_ctrl() */
+ u32 umcg_flags;
clockid_t umcg_clock;
struct umcg_task __user *umcg_task;
--- a/include/uapi/linux/umcg.h
+++ b/include/uapi/linux/umcg.h
@@ -133,11 +133,13 @@ struct umcg_task {
* @UMCG_CTL_REGISTER: register the current task as a UMCG task
* @UMCG_CTL_UNREGISTER: unregister the current task as a UMCG task
* @UMCG_CTL_WORKER: register the current task as a UMCG worker
+ * @UMCG_CTL_LAZY: don't wake server on runnable enqueue
*/
enum umcg_ctl_flag {
UMCG_CTL_REGISTER = 0x00001,
UMCG_CTL_UNREGISTER = 0x00002,
UMCG_CTL_WORKER = 0x10000,
+ UMCG_CTL_LAZY = 0x20000,
};
#endif /* _UAPI_LINUX_UMCG_H */
--- a/kernel/sched/umcg.c
+++ b/kernel/sched/umcg.c
@@ -416,6 +416,27 @@ static int umcg_enqueue_runnable(struct
}
/*
+ * Enqueue tsk to it's server's runnable list and wake the server for pickup if
+ * so desired. Notable LAZY workers will not wake the server and rely on the
+ * server to do pickup whenever it naturally runs next.
+ *
+ * Returns:
+ * 0: success
+ * -EFAULT
+ */
+static int umcg_enqueue_and_wake(struct task_struct *tsk, bool force)
+{
+ int ret = umcg_enqueue_runnable(tsk);
+ if (ret)
+ return ret;
+
+ if (force || !(tsk->umcg_flags & UMCG_CTL_LAZY))
+ ret = umcg_wake_server(tsk);
+
+ return ret;
+}
+
+/*
* umcg_wait: Wait for ->state to become RUNNING
*
* Returns:
@@ -522,12 +543,8 @@ void umcg_sys_exit(struct pt_regs *regs)
if (umcg_update_state(tsk, self, UMCG_TASK_BLOCKED, UMCG_TASK_RUNNABLE))
UMCG_DIE_UNPIN("state");
- if (umcg_enqueue_runnable(tsk))
- UMCG_DIE_UNPIN("enqueue");
-
- /* Server might not be RUNNABLE, means it's already running */
- if (umcg_wake_server(tsk))
- UMCG_DIE_UNPIN("wake-server");
+ if (umcg_enqueue_and_wake(tsk, false))
+ UMCG_DIE_UNPIN("enqueue-and-wake");
umcg_unpin_pages();
@@ -582,15 +599,11 @@ void umcg_notify_resume(struct pt_regs *
UMCG_TASK_RUNNABLE))
UMCG_DIE_UNPIN("state");
- if (umcg_enqueue_runnable(tsk))
- UMCG_DIE_UNPIN("enqueue");
-
/*
- * XXX do we want a preemption consuming ::next_tid ?
- * I'm currently leaning towards no.
+ * Preemption relies on waking the server on enqueue.
*/
- if (umcg_wake_server(tsk))
- UMCG_DIE_UNPIN("wake-server");
+ if (umcg_enqueue_and_wake(tsk, true))
+ UMCG_DIE_UNPIN("enqueue-and-wake");
umcg_unpin_pages();
}
@@ -686,23 +699,15 @@ SYSCALL_DEFINE2(umcg_wait, u32, flags, u
goto unpin;
if (worker) {
- ret = umcg_enqueue_runnable(tsk);
+ ret = umcg_enqueue_and_wake(tsk, !tsk->umcg_next);
if (ret)
goto unpin;
}
- if (worker)
- ret = umcg_wake(tsk);
- else if (tsk->umcg_next)
+ if (tsk->umcg_next) {
ret = umcg_wake_next(tsk);
-
- if (ret) {
- /*
- * XXX already enqueued ourself on ::server_tid; failing now
- * leaves the lot in an inconsistent state since it'll also
- * unblock self in order to return the error. !?!?
- */
- goto unpin;
+ if (ret)
+ goto unpin;
}
umcg_unpin_pages();
@@ -783,7 +788,8 @@ SYSCALL_DEFINE3(umcg_ctl, u32, flags, st
if (flags & ~(UMCG_CTL_REGISTER |
UMCG_CTL_UNREGISTER |
- UMCG_CTL_WORKER))
+ UMCG_CTL_WORKER |
+ UMCG_CTL_LAZY))
return -EINVAL;
if (flags == UMCG_CTL_UNREGISTER) {
@@ -827,7 +833,7 @@ SYSCALL_DEFINE3(umcg_ctl, u32, flags, st
rcu_read_lock();
server = find_task_by_vpid(ut.server_tid);
if (server && server->mm == current->mm) {
- if (flags == UMCG_CTL_WORKER) {
+ if (flags & UMCG_CTL_WORKER) {
if (!server->umcg_task ||
(server->flags & PF_UMCG_WORKER))
server = NULL;
@@ -843,10 +849,11 @@ SYSCALL_DEFINE3(umcg_ctl, u32, flags, st
if (!server)
return -ESRCH;
- if (flags == UMCG_CTL_WORKER) {
+ if (flags & UMCG_CTL_WORKER) {
if ((ut.state & (UMCG_TASK_MASK | UMCG_TF_MASK)) != UMCG_TASK_BLOCKED)
return -EINVAL;
+ current->umcg_flags = flags & UMCG_CTL_LAZY;
WRITE_ONCE(current->umcg_task, self);
current->flags |= PF_UMCG_WORKER; /* hook schedule() */
set_syscall_work(SYSCALL_UMCG); /* hook syscall */
@@ -858,6 +865,7 @@ SYSCALL_DEFINE3(umcg_ctl, u32, flags, st
if ((ut.state & (UMCG_TASK_MASK | UMCG_TF_MASK)) != UMCG_TASK_RUNNING)
return -EINVAL;
+ current->umcg_flags = 0;
WRITE_ONCE(current->umcg_task, self);
set_thread_flag(TIF_UMCG); /* hook return-to-user */
next prev parent reply other threads:[~2021-12-15 10:07 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 20:44 Peter Zijlstra
2021-12-14 20:44 ` [RFC][PATCH 1/3] sched/umcg: add WF_CURRENT_CPU and externise ttwu Peter Zijlstra
2021-12-14 20:44 ` [RFC][PATCH 2/3] x86/uaccess: Implement unsafe_try_cmpxchg_user() Peter Zijlstra
2021-12-20 17:30 ` Sean Christopherson
2021-12-21 11:17 ` Peter Zijlstra
2021-12-14 20:44 ` [RFC][PATCH 3/3] sched: User Mode Concurency Groups Peter Zijlstra
2021-12-21 17:19 ` Peter Oskolkov
2022-01-14 14:09 ` Peter Zijlstra
2022-01-14 15:16 ` Peter Zijlstra
2022-01-14 17:15 ` Peter Zijlstra
2022-01-17 11:35 ` Peter Zijlstra
2022-01-17 12:22 ` Peter Zijlstra
2022-01-17 12:12 ` Peter Zijlstra
2022-01-18 10:09 ` Peter Zijlstra
2022-01-18 18:19 ` Peter Oskolkov
2022-01-19 8:47 ` Peter Zijlstra
2022-01-19 17:33 ` Peter Oskolkov
2022-01-19 8:51 ` Peter Zijlstra
2022-01-19 8:59 ` Peter Zijlstra
2022-01-19 17:52 ` Peter Oskolkov
2022-01-20 10:37 ` Peter Zijlstra
2022-01-17 13:04 ` Peter Zijlstra
2021-12-24 11:27 ` Peter Zijlstra
2021-12-14 21:00 ` [RFC][PATCH 0/3] sched: User Managed Concurrency Groups Peter Zijlstra
2021-12-15 3:46 ` Peter Oskolkov
2021-12-15 10:06 ` Peter Zijlstra [this message]
2021-12-15 13:03 ` Peter Zijlstra
2021-12-15 17:56 ` Peter Oskolkov
2021-12-15 18:18 ` Peter Zijlstra
2021-12-15 19:49 ` Peter Oskolkov
2021-12-15 22:25 ` Peter Zijlstra
2021-12-15 23:26 ` Peter Oskolkov
2021-12-16 13:23 ` Thomas Gleixner
2021-12-15 18:25 ` Peter Zijlstra
2021-12-15 21:04 ` Peter Oskolkov
2021-12-15 23:16 ` Peter Zijlstra
2021-12-15 23:31 ` Peter Oskolkov
2021-12-15 10:44 ` Peter Zijlstra
2021-12-15 13:49 ` Matthew Wilcox
2021-12-15 17:54 ` 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=Ybm+HJzkO/0BB4Va@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--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=pjt@google.com \
--cc=posk@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox