From: Peter Zijlstra <peterz@infradead.org>
To: Joel Fernandes <joel@joelfernandes.org>
Cc: Hugh Dickins <hughd@google.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: config SCHED_CORE
Date: Sun, 23 May 2021 12:57:04 +0200 [thread overview]
Message-ID: <YKo1AOIIsZectSQt@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAEXW_YRxOqQCF2FgXAjL3xkZhRD4rdFuxvyPd-ESXYQQ78cyfQ@mail.gmail.com>
On Fri, May 21, 2021 at 07:57:35AM -0400, Joel Fernandes wrote:
> On Fri, May 21, 2021 at 3:53 AM Peter Zijlstra <peterz@infradead.org> wrote:
> > + help
> > + This option enables Core scheduling, a means of coordinated task
> > + selection across SMT siblings with the express purpose of creating a
> > + Core wide privilidge boundary. When enabled -- see prctl(PR_SCHED_CORE)
> > + -- task selection will ensure all SMT siblings will execute a task
> > + from the same 'core group', forcing idle when no matching task is found.
> > +
> > + This provides means of mitigation against a number of SMT side-channels;
> > + but is, on its own, insufficient to mitigate all known side-channels.
> > + Notable: the MDS class of attacks require more.
> > +
> > + Default enabled for anything that has SCHED_SMT, when unused there should
> > + be no impact on performance.
>
> This description sort of makes it sound like security is the only
> usecase. Perhaps we can also add here that core-scheduling can help
> performance of workloads where hyperthreading is undesired, such as
> when VM providers don't want to share hyperthreads.
Something like so then?
---
kernel/Kconfig.preempt | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/kernel/Kconfig.preempt b/kernel/Kconfig.preempt
index ea1e3331c0ba..cd497fecfd43 100644
--- a/kernel/Kconfig.preempt
+++ b/kernel/Kconfig.preempt
@@ -104,4 +104,18 @@ config SCHED_CORE
bool "Core Scheduling for SMT"
default y
depends on SCHED_SMT
+ help
+ This option enables Core scheduling, a means of coordinated task
+ selection across SMT siblings. When enabled -- see
+ prctl(PR_SCHED_CORE) -- task selection will ensure all SMT siblings
+ will execute a task from the same 'core group', forcing idle when no
+ matching task is found.
+
+ Use of this feature includes:
+ - mitigation of some (not all) SMT side channels;
+ - limiting SMT interference to improve determinism and/or performance.
+
+ Default enabled for anything that has SCHED_SMT, when unused there
+ should be no impact on performance.
+
next prev parent reply other threads:[~2021-05-23 10:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 3:06 config SCHED_CORE Hugh Dickins
2021-05-21 7:53 ` Peter Zijlstra
2021-05-21 11:18 ` Joel Fernandes
2021-05-21 11:57 ` Joel Fernandes
2021-05-21 13:33 ` Peter Zijlstra
2021-05-24 20:50 ` Joel Fernandes
2021-05-23 10:57 ` Peter Zijlstra [this message]
2021-05-23 20:30 ` Hugh Dickins
2021-05-23 21:31 ` Randy Dunlap
2021-05-21 16:09 ` Randy Dunlap
2021-05-25 7:05 ` [PATCH] sched: Add CONFIG_SCHED_CORE help text Peter Zijlstra
2021-05-25 17:24 ` Randy Dunlap
2021-05-25 22:17 ` Hugh Dickins
2021-06-01 14:04 ` [tip: sched/core] " tip-bot2 for 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=YKo1AOIIsZectSQt@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=hughd@google.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.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